lp:~cbelu/charm-k8s-ingress
- Get this repository:
-
git clone
https://git.launchpad.net/~cbelu/charm-k8s-ingress
Branches
Name | Last Modified | Last Commit |
---|---|---|
improve-coverage | 2022-02-24 15:03:20 UTC |
Improves the test code coverage
Author:
Claudiu Belu
Improves the test code coverage There are a few cases in which the test coverage could be improved. |
additional- |
2022-02-24 15:00:51 UTC |
Fixes adding unwanted routes from additional-hostnames
Author:
Claudiu Belu
Fixes adding unwanted routes from additional- On multiple ingress relations for different service-hostnames (foo, bar), This is happening because the same list of ingress paths are being used When creating the Ingress Objects, a separate path list list is created for |
fixes-missing- |
2022-02-24 13:53:51 UTC |
Fixes Resource creation on missing relation data
Author:
Claudiu Belu
Fixes Resource creation on missing relation data At the moment, the charm will attempt to create Kubernetes Resources for Skip adding resources for relations we don't have valid data from. |
multiple-relations | 2022-02-15 12:36:23 UTC |
Adds multiple ingress relations support
Author:
Claudiu Belu
Adds multiple ingress relations support Removes the 1 limit from metadata.yaml Currently, the Ingress Name is based on the service-name. However, that The nginx/nginx-ingress Controller typically used in EKS doesn't handle This charm will now group all the Ingress rules by the required hostnames Creates a single Kubernetes Ingress Resource containing all the hosts and Adds TLS information for each additional-hostname defined (each new hostname On multiple relations, if we're required to have different annotations On multiple relations, if there are multiple matching route paths on the Adds unit tests to validate the cases in which multiple relations are being On multiple relations, we should use the service-name, service-port, If there is only one relation, the config option will still override [1] https:/ |
1 → 4 of 4 results | First • Previous • Next • Last |