Releases: c6o/helm-charts
Releases · c6o/helm-charts
0.8.0
What's Changed
- uses a Kubernetes operator for managing serves by default. With the operator serves are a custom resource on a Kubernetes cluster. E.g.
kubectl get serves -n <namepace>
shows all current serves in a namespace.
Full Changelog: 0.7.0...0.8.0
0.7.0
What's Changed
- docs: add minimal chart documentation by @georg in #48
- fix: missing space by @georg in #49
- chore: add flag for running with operator by @kramuenke in #45
- chore: release 0.7.0 by @gtrrz-victor in #50
Full Changelog: 0.6.0...0.7.0
0.6.0
What's Changed
- run app version 2.5.2
- added option to run the router pod of Codezero Space Agent with privileged access. By default, the router pod runs with a security context with only the NET_BIND_SERVICE capability. This is not guaranteed to work on all clusters. When the
router.privilegedAccess
option is set to true in the Codezero Helm chart values, the router pods are started with an empty security context.
0.5.3
0.5.2
0.5.1
What's Changed
- fix: set
allowPrivilegeEscalation
insecurityContext
to false
Full Changelog: 0.5.0...0.5.1
0.5.0
What's Changed
- feat: New default for
securityContext
for all containers by settingsecurityContext
to a compliant restricted policy. This should alleviate install errors when running a pod security admission controller. The new default is:
securityContext:
runAsNonRoot: true
runAsUser: 1000
runAsGroup: 1000
allowPrivilegeEscalation: true
capabilities:
drop:
- ALL
seccompProfile:
type: RuntimeDefault
- fix: adds security context to init containers
- fix: moves opa configuration out of orchestrator
Full Changelog: 0.4.1...0.5.0