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.

Sign up for GitHub

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

chore(docs): Update install docs with arguments #1158

Open
wants to merge 3 commits into
base: develop
Choose a base branch
from
Open

chore(docs): Update install docs with arguments #1158

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b2d6e56
chore(docs): Update install docs with arguments
May 8, 2023
bda312a
Merge branch 'develop' into chore-update-docs
dev-slatto May 8, 2023
e2d956c
Merge branch 'develop' into chore-update-docs
gaurav-splunk May 26, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,6 +116,8 @@ A Kubernetes cluster administrator can install and start the Splunk Operator for
kubectl apply -f https://github.com/splunk/splunk-operator/releases/download/2.2.1/splunk-operator-cluster.yaml --server-side --force-conflicts
```

The reason for appending `--server-side` and `--force-conflicts` to the apply command is that some of the CRDs are getting to long according to the CRD standards. There are no real implications caused by this.

The [Advanced Installation Instructions](Install.md) page offers guidance for advanced configurations, including the use of private image registries, installation at cluster scope, and installing the Splunk Operator as a user who is not a Kubernetes administrator. Users of Red Hat OpenShift should review the [Red Hat OpenShift](OpenShift.md) page.

*Note: We recommended that the Splunk Enterprise Docker image is copied to a private registry, or directly onto your Kubernetes workers before creating large Splunk Enterprise deployments. See the [Required Images Documentation](Images.md) page, and the [Advanced Installation Instructions](Install.md) page for guidance on working with copies of the Docker images.*
Expand Down