Update ingress apiVersion and make hardcoded variables dynamic #64
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Use networking.k8s.io/v1 version for ingress. This PR completes the upgrade to the new ingress apiVersion started in openstad/openstad-kubernetes#71.
IMPORTANT: This requires Kubernetes version v1.19 due to switching from networking.k8s.io/v1beta1 to networking.k8s.io/v1.
See https://kubernetes.io/docs/reference/using-api/deprecation-guide/#ingress-v122 for more details.
Some ingress values (service name & port for instance) were hardcoded. This PR also uses the already available environment variables to build these ingress values if needed (and falls back to the hardcoded values if they're not). This also fixes the
systemIngresses
array which caused namespaced installations to have theirsystemIngresses
removed, due to not beingopenstad-frontend
butopenstad-NAMESPACE-frontend
.Issue reference
Type of change
feature
Documentation
No updated documentation - changelog is updated
Tests
Locally & test cluster
Branch