Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Teleport Operator to teleport-cluster Helm chart #12144

Closed

Conversation

marcoandredinis
Copy link
Contributor

No description provided.

@marcoandredinis marcoandredinis force-pushed the marco/plugins-teleport-operator-charts branch 8 times, most recently from f05b0b0 to 4c8c4a5 Compare April 28, 2022 13:41
@marcoandredinis marcoandredinis force-pushed the marco/plugins-teleport-operator-charts branch 3 times, most recently from 59cbb2d to 0ae86ca Compare May 4, 2022 07:53
@marcoandredinis marcoandredinis force-pushed the marco/plugins-teleport-operator-charts branch from 0ae86ca to ce9b679 Compare May 11, 2022 09:25
@marcoandredinis marcoandredinis force-pushed the marco/plugins-teleport-operator-charts branch 8 times, most recently from 45406a1 to 28b266b Compare May 30, 2022 15:16
@marcoandredinis marcoandredinis force-pushed the marco/plugins-teleport-operator-charts branch 7 times, most recently from 5ebf5d2 to e624d08 Compare June 6, 2022 15:43
@marcoandredinis marcoandredinis force-pushed the marco/plugins-teleport-operator-charts branch 2 times, most recently from 13e6a4f to 5179f91 Compare June 7, 2022 15:22
We are going to use a sidecar architecture to run the Operator.

It will have privileged access because it runs right next to the
Teleport Auth Server, sharing the data dir (`/var/lib/teleport`) and its
configuration (`/etc/teleport/teleport.yaml`).

This will allow us to create the necessary user and role, and an
identity file which the operator will use to create a teleport client
and manage the cluster.
We require the CRDs to be installed to be able to use the operator.

We are now installing the CRDs when the app starts

Right now, we upsert the current version embedded in the binary
This adds new build targets:
- image-operator-ci: builds an image containing the operator
- publish-operator-ci: push the image into the registry

The target `publish-operator-ci` gets called when in the
`build-docker-images` pipeline
This creates an image at:
quay.io/gravitational/teleport-operator-ci:<version>

Then, it gets retagged as
quay.io/gravitational/teleport-operator:<version>
which is the user facing image.
This last step happens in the `promot-build` pipeline.
This commit adds a test for the CRD autogeneration
It uses the current types.proto version and asserts it has no diff
compared to the golden files generated locally.
@marcoandredinis marcoandredinis force-pushed the marco/plugins-teleport-operator-charts branch from 027e99f to d4fd836 Compare June 29, 2022 09:35
@marcoandredinis marcoandredinis force-pushed the marco/plugins-teleport-operator-charts branch from d4fd836 to 342c6c1 Compare June 29, 2022 09:40
Changes the Teleport Cluster chart to, optionally, include the
teleport-operator.

It adds the CRDs as subchart conditionally loaded only if the operator
flag is set to true.

Adds a guide on how to use the Operator within the Teleport Cluster
chart.
@marcoandredinis marcoandredinis force-pushed the marco/plugins-teleport-operator-charts branch from 342c6c1 to fc9d67f Compare June 29, 2022 09:46
@marcoandredinis marcoandredinis force-pushed the marco/operator branch 3 times, most recently from a44f244 to 0de2318 Compare June 30, 2022 14:23
@hugoShaka hugoShaka force-pushed the marco/operator branch 2 times, most recently from f5d23e4 to e1f288c Compare July 18, 2022 14:39
@marcoandredinis marcoandredinis deleted the marco/plugins-teleport-operator-charts branch August 18, 2022 06:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant