This repository has been archived by the owner on Oct 22, 2021. It is now read-only.
Releases: cloudfoundry-incubator/quarks-operator
Releases · cloudfoundry-incubator/quarks-operator
v0.4.2
New Features
- CRDs are managed by the operator binary, not the helm chart
- Fix for ExtendedJobs not persisting pod output properly
- Separation between the operator's namespace and the "watched namespace"
Known Issues
helm delete
won't clean up Custom Resource Definitions- updates may cause skipping of StatefulSet version numbers
- high availability not supported for instance groups that have active/passive replicas
Installation
helm install --namespace cf-operator --name cf-operator https://s3.amazonaws.com/cf-operators/release/helm-charts/cf-operator-v0.4.2%2B0.g604925f0.tgz
Assets
Helm chart and standalone binary:
v0.4.0
New Features
- improved log printing in the logging sidecar
- logging sidecar can be turned off
- support for "pre render" scripts in BOSH Deployments (used to patch jobs, templates or BPM info on-the-fly)
- "anchor compression" for manifests, drastically reducing the size of manifest secrets
- support for post-start scripts
- support for arbitrary kubernetes
env
items in BPM processes (supports the downward API) - the
bosh_containerization
key is now namedquarks
- performance improvements for resolving "Desired Manifests"
- updating implicit variables now trigger updates for BOSH Deployments
- using dumb-init as PID 1 for all containers
- fixed the operatos's readiness probe
- improved BOSH/BPM volume management
- ExtendedSecrets can use Kubernetes to sign certificates
- Instance Groups can now explicitely set the Kubernetes Security Context of their respective pods
- Pod Service Account for Instance Groups is configurable
Known Issues
helm delete
won't clean up Custom Resource Definitions- updates may cause skipping of StatefulSet version numbers
- high availability not supported for instance groups that have active/passive replicas
Installation
# Use this if you've never installed the operator before
helm install --namespace cf-operator --name cf-operator https://cf-operators.s3.amazonaws.com/release/helm-charts/cf-operator-v0.4.0%2B1.g3d277af0.tgz
# Use this if the custom resources have already been created by a previous CF Operator installation
helm install --namespace cf-operator --name cf-operator https://cf-operators.s3.amazonaws.com/release/helm-charts/cf-operator-v0.4.0%2B1.g3d277af0.tgz --set "customResources.enableInstallation=false"
Assets
Helm chart and standalone binary:
v0.3.0
New Features
- ability to provide/override BPM configuration for processes using a property key below
bosh_containerization
- better names for secrets created by the operator
- volumes are now created based on instance group and BPM information
- volumes are correctly mounted in init containers
- support for pre-start hooks (both BOSH and BPM flavors)
- support for drain hooks
- operator now has a health endpoint, and it's used for a readiness probe in the helm chart
- helm chart allows the user to skip CRD installation
- stability improvements (we're no longer using finalizers)
- improved labels and annotations for resources
Known Issues
helm delete
won't clean up Custom Resource Definitions- updates may cause skipping of StatefulSet version numbers
- high availability not supported for instance groups that have active/passive replicas
Installation
# Use this if you've never installed the operator before
helm install --namespace cf-operator --name cf-operator https://s3.amazonaws.com/cf-operators/helm-charts/cf-operator-v0.3.0%2B1.g551e559.tgz
# Use this if the custom resources have already been created by a previous CF Operator installation
helm install --namespace cf-operator --name cf-operator https://s3.amazonaws.com/cf-operators/helm-charts/cf-operator-v0.3.0%2B1.g551e559.tgz --set "customResources.enableInstallation=false"
v0.2.2
New Features
- fixes for BOSH-specific directory structures
- making a change in a ConfigMap referenced by a BOSHDeployment correctly results in new StatefulSet versions for BOSH Instance Groups
- BPM and Instance Group definitions are now stored in separate Secrets
.Values.image.pullPolicy
used correctly in the Helm chart- support for multiple BPM processes per BOSH Job (they result in multiple containers in a Pod)
- link functions are properly rendered when BOSH Jobs are missing from a deployment
- helm chart installs a readiness probe for the operator
Known Issues
- might not work with Kube 1.14.*
helm delete
won't clean up Custom Resource Definitions- updates may cause skipping of StatefulSet version numbers
Installation
helm install --namespace cf-operator --name cf-operator https://s3.amazonaws.com/cf-operators/helm-charts/cf-operator-v0.2.2%2B47.g24492ea.tgz
v0.2.1
New Features
- helm chart available as tgz, can be installed in one line
- no more
latest
tag - operator images are immutable - improved management of PVCs for ExtendedStatefulSets
Known Issues
- updates may cause superfluous restarts of pods
Installation
helm install --namespace cf-operator --name cf-operator https://s3.amazonaws.com/cf-operators/helm-charts/cf-operator-v0.2.0%2B73.gb3dfed5.tgz
v0.2.0
New Features
- helm chart available for download [1]
- update support for BOSH Deployments
- services are created for BOSH instance groups
- list of curated examples that are tested on each build [2]
Known Issues
- updates may cause superfluous restarts of pods
- helm chart needs to be downloaded and unpacked, can't be installed from URL
[1] https://s3.amazonaws.com/cf-operators/helm-charts/cf-operator-v0.2.0%2B0.g8455b1f.zip
[2] https://github.com/cloudfoundry-incubator/cf-operator/tree/master/docs/examples
v0.1.0
New Features
- working implementations for
ExtendedStatefulSet
,ExtendedJob
andExtendedSecret
- end-to-end flow for deploying a
BOSHDeployment
Known Issues
- update flow for a
BOSHDeployment
doesn't work - not all BPM information is used when running containers