Releases: giantswarm/chart-operator
Releases · giantswarm/chart-operator
v3.3.0
Added
- Added and enabled by default an
emptyDir
volume undertmp
of the deployment for artifact pulls
so that we can make the rest of the root file system read only under the security context. - Added control over the VPA max allowed resources.
Changed
- Requests and limits are always set on the deployment.
- Increased default requests and limits because of the introduction of the
emptyDir
volume under/tmp
. - Enabled read only root file system by default on the security context.
- Update PolicyExceptions to v2 and fallback to v2beta1.
v3.2.1
Fixed
- Use separate rest configs for different Kubernetes clients.
v3.2.0
Added
- Added
--service.controller.resyncperiod
daemon flag that can be controller via.controller.resyncPeriod
Helm value.
Controls the duration after which a complete sync with all known runtime objects the controller watches is performed.
Defaults to5m
.
v3.1.3
Fixed
- Move pss values under the global property
Changed
- Use base images from
gsoci.azurecr.io
v3.1.2
Changed
- Configure
gsoci.azurecr.io
as the default container image registry.
v3.1.1
Changed
- Configure gsoci.azurecr.io as the registry to use by default
v3.1.0
v3.0.0
Removed
- Removed
giantswarm.io/monitoring: "true"
label from theService
resource. To get metricschart-operator
should
be from now on used in conjunction withchart-operator-extensions
versionv1.1.1
or later to deploy
ServiceMonitor
resource for it. It was split up aschart-operator
is one of the first component to get into
a cluster that will deploy most other things, for example Prometheus that will eventually actually deploy the
CRD forServiceMonitor
.