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

CockroachDB License Configuration #51

Closed
johnrk-zz opened this issue Jul 10, 2020 · 4 comments
Closed

CockroachDB License Configuration #51

johnrk-zz opened this issue Jul 10, 2020 · 4 comments

Comments

@johnrk-zz
Copy link
Contributor

johnrk-zz commented Jul 10, 2020

As an operator, I can configure CockroachDB license on a new
CockroachDB cluster in Kubernetes, so that I initialize a cluster that
meets my expected deployment needs.

Customers need to be able to apply an enterprise license that exist in cluster settings (enterprise.license).

@johnrk-zz johnrk-zz added this to To do in Kubernetes Operator via automation Jul 10, 2020
@johnrk-zz johnrk-zz added this to To do in Cockroach Kubernetes Operator via automation Jul 14, 2020
@johnrk-zz johnrk-zz removed this from To do in Kubernetes Operator Jul 14, 2020
@johnrk-zz johnrk-zz changed the title Operator Configuration of CockroachDB Cluster Settings Operator Configuration of CockroachDB License Jul 15, 2020
@johnrk-zz johnrk-zz changed the title Operator Configuration of CockroachDB License CockroachDB License Configuration Jul 15, 2020
@johnrk-zz
Copy link
Contributor Author

@keith-mcclellan , isn't this required for our certifications?

@johnrk-zz johnrk-zz moved this from Triage to Low Priority in Cockroach Kubernetes Operator Jan 28, 2021
@chrislovecnm
Copy link
Contributor

@johnrk they can add the license was as an argument. Can we please test this?

@chrislovecnm chrislovecnm added the next release This issue is for the next release label Feb 1, 2021
@keith-mcclellan
Copy link
Contributor

The only way I know of to do this would be to set an environment variable argument in the CR, which would expose the license as plain text to anyone with access to the openshift namespace. Not sure that's what we want to recommend here.

@keith-mcclellan keith-mcclellan removed the next release This issue is for the next release label Feb 1, 2021
@pseudomuto
Copy link
Contributor

This has gone kind of stale, so I'm going to close it for now. Feel free to reopen if you think the operator needs to handle this.

For now, since this is a one time operation, I think people can do the following:

# deploy the secure client
kubectl create \
  -f https://raw.githubusercontent.com/cockroachdb/cockroach-operator/master/examples/client-secure-operator.yaml

# open db console
kubectl exec -it cockroachdb-client-secure \
  -- ./cockroach sql \
  --certs-dir=/cockroach/cockroach-certs \
  --host=cockroachdb-public

# set license details
SET CLUSTER SETTING cluster.organization = '<YOUR_ORG>';
SET CLUSTER SETTING enterprise.license = '<YOUR_LICENCE_KEY>';

Cockroach Kubernetes Operator automation moved this from Low Priority to Done Nov 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants