-
Notifications
You must be signed in to change notification settings - Fork 72
[Feature] [Platform] Do not require LM during install commands #1989
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -99,7 +99,11 @@ in the [kube-arangodb repository](https://github.com/arangodb/kube-arangodb/rele | |||||
| After deploying the latest ArangoDB Kubernetes operator, use the command below to deploy your [license key](https://docs.arangodb.com/stable/operations/administration/license-management/) as a secret which is required for the Enterprise Edition starting with version 3.9: | ||||||
|
|
||||||
| ```bash | ||||||
| # For the License Key | ||||||
| kubectl create secret generic arango-license-key --from-literal=token-v2="<license-string>" | ||||||
|
|
||||||
| # For the License Manager Key | ||||||
| kubectl create secret generic arango-license-key --from-literal=license-client-id="<license-client-id>" --from-literal=license-client-secret="<license-client-secret>" | ||||||
|
||||||
| kubectl create secret generic arango-license-key --from-literal=license-client-id="<license-client-id>" --from-literal=license-client-secret="<license-client-secret>" | |
| kubectl create secret generic arango-license-manager-key --from-literal=license-client-id="<license-client-id>" --from-literal=license-client-secret="<license-client-secret>" |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,27 @@ | ||
| // | ||
| // DISCLAIMER | ||
| // | ||
| // Copyright 2025 ArangoDB GmbH, Cologne, Germany | ||
| // | ||
| // Licensed under the Apache License, Version 2.0 (the "License"); | ||
| // you may not use this file except in compliance with the License. | ||
| // You may obtain a copy of the License at | ||
| // | ||
| // http://www.apache.org/licenses/LICENSE-2.0 | ||
| // | ||
| // Unless required by applicable law or agreed to in writing, software | ||
| // distributed under the License is distributed on an "AS IS" BASIS, | ||
| // WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
| // See the License for the specific language governing permissions and | ||
| // limitations under the License. | ||
| // | ||
| // Copyright holder is ArangoDB GmbH, Cologne, Germany | ||
| // | ||
|
|
||
| package cli | ||
|
|
||
| import "github.com/arangodb/kube-arangodb/pkg/logging" | ||
|
|
||
| var ( | ||
| logger = logging.Global().RegisterAndGetLogger("cli-utils", logging.Info) | ||
| ) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The examples for both license key types use the same secret name
arango-license-key. This will cause a conflict if users try to create both secrets. Consider using different secret names (e.g.,arango-license-keyandarango-license-manager-key) or clarifying that only one should be used at a time.