- A user-friendly description of a new feature. {issue-number}
- A user-friendly description of a fix. {issue-number}
- A user-friendly description of a security fix. {issue-number}
- API and Sync containers now have liveness and readiness probes. {#47}
- The Connect API can now be configured to use TLS with a custom certificate.
- Connect server updated to
v1.2.0{#49} - Resource limits can now be set on the operator {#52}
- Additional labels & annotations are set for deployments {#51}
- Follow principle of least privilege for operator permissions {#55}
- New Helm repo URL: https://1password.github.io/connect-helm-charts {#41}
- Connect server updated to
v1.1.0{#40} - Operator version updated to
v1.0.1{#42} - CRD now lives in
crds/dir, so they can be skipped with the--skip-crdsflag {#36} - RBAC resources will be created by default when operator is enabled {#37}
.Release.Namespaceis now watched by the operator by default {#32}
- Connect's chart readme should now show up on ArtifactHub.
- Helm's native
.Release.Namespaceis now used for setting the Chart's namespace. {#13} - A Node selector stanza can be used for the Connect and Operator pods.
- Setting a token for the operator has been clarified in the readme. {#16}
- Resources now follow Helm's best practice for standard labels. {#11}
- The fixed port value for the NodePort service has been removed to resolve conflicts with previously initialized services. Kubernetes will now automatically choose a free port. {#22}
- Security Context was added to all containers to limit their default permissions. {#25}
- Typo fixes for README
- Update app name to Connect
- Ability to deploy Connect via helm
- Ability to deploy Kuberenetes operator via helm
- Automate creation of secrets for connect credentials and operator token
- Readme update
- Updating to use latest Connect and Connect Operator versions