Adding said label, that's already defined, to the deployments themselves.
This will enable Armada to properly wait for certain percentages of the
deployment replicas to be ready prior to proceeding. Prior to this change,
there wasn't a way to select these deployments via labels.
Change-Id: I4d8e479eb40e4395a4e3b79bbc9df651aa4e12e7
This change fixes a few issues with the MAAS chart:
1. Removes extraneous serviceName from maas-ingress-errors Deployment
2. Adds missing serviceName to maas-syslog StatefulSet
3. Moves maas-region-api Ingress object back under extensions/v1beta1
Similar to: https://review.opendev.org/691701/
Change-Id: I83156c0e255ad17bbac024daba293490980414ee
'apps/v1beta1' apiVersion for Deployment has been deprecated.
'extensions/v1beta1' apiVersion for Ingress resource has been deprecated.
This PS aligns towards the effort in moving to k8s 1.16.
Reference: https://v1-14.docs.kubernetes.io/docs/setup/release/notes/#deprecations
Change-Id: Ied31e4e136fb9bf0343d609cf75bd1b7028d6f66
Updating deployment-ingress-errors chart so ingress-errors deploys.
The chart was previously checking for rack_deployment which is now
rack_statefulset.
Change-Id: I79750804ca7bb62a7fcf9c91b80a435d9af332aa
Run the maas-ingress and maas-ingress-vip containers with the
'www-data' (33) user
Run the maas-ingress-errors container with the error-page image [0],
from [1] which already runs as nobody user.
[0] Dockerfile.404-server-with-metrics
[1] https://github.com/kubernetes/ingress-gce
Change-Id: Idf3791a958017d512bb3f5015b59452e2831b1b3
- deployment-ingress-errors.yaml
This updates the maas chart to include the pod
security context on the pod template.
This also adds the container security context to set
readOnlyRootFilesystem to true
Change-Id: Id377f31aacc65e8ba31a360d9283fda225e7732a
Upgrades to the MAAS chart to allow for the Pods
running the rack and region services to work across
all control plane hosts.
Change-Id: I84c856599a1122a2b4a64242a7cea357887b0462
DeJaeger, Darren (dd118r)