connect-1.4.0

Features

• 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-1.3.0

Features

• 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}

Security

• Follow principle of least privilege for operator permissions {#55}

connect-1.2.0

Features

• 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-crds flag {#36}
• RBAC resources will be created by default when operator is enabled {#37}
• .Release.Namespace is now watched by the operator by default {#32}

connect-1.1.0

Features

• Connect's chart readme should now show up on ArtifactHub.
• Helm's native .Release.Namespace is 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}

Fixes

• 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

• Security Context was added to all containers to limit their default permissions. {#25}

connect-1.0.1

Features

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

onepassword-connect-0.0.1

A Helm chart for deploying 1Password Connect and the 1Password Connect Kubernetes Operator