Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
5 changes: 4 additions & 1 deletion docs/ChangeLog.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
## 1.0.2 (2021-08-20)
* This is the 1.0.2 release. The Splunk Operator for Kubernetes is a supported platform for deploying Splunk Enterprise with the prerequisites and constraints laid out [here](https://github.com/splunk/splunk-operator/blob/develop/docs/README.md#prerequisites-for-the-splunk-operator)

* This release depends upon changes made concurrently in the Splunk Enterprise container images. You should use the splunk/splunk:8.2.1-a1 image with it
* This release depends upon changes made concurrently in the Splunk Enterprise container images. You should use the splunk/splunk:8.2.1-a2 image with it

* CSPL-725 - Operator App Management Framework Phase 2 (Beta Release)

Expand All @@ -13,6 +13,9 @@
* Updated documentation for App Framework
* Updated documentation for Smartstore examples

* Known Issues
* CSPL-1250 - [AppFramework] On App install/update to the Search Head Cluster(SHC), the deployer unnecessarily includes the apps which were installed in the previous bundle push along with the new/updated app. This can potentially delay the app install/update process

## 1.0.1 (2021-06-09)
* This is the 1.0.1 release. The Splunk Operator for Kubernetes is a supported platform for deploying Splunk Enterprise with the prerequisites and constraints laid out [here](https://github.com/splunk/splunk-operator/blob/develop/docs/README.md#prerequisites-for-the-splunk-operator)

Expand Down
2 changes: 1 addition & 1 deletion docs/Images.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
The Splunk Operator requires these docker images to be present or available to your Kubernetes cluster:

* `splunk/splunk-operator`: The Splunk Operator image built by this repository or the [official release](https://hub.docker.com/r/splunk/splunk-operator) (1.0.2 or later)
* `splunk/splunk:<version>`: The [Splunk Enterprise image](https://github.com/splunk/docker-splunk) (8.2.1-a1 or later)
* `splunk/splunk:<version>`: The [Splunk Enterprise image](https://github.com/splunk/docker-splunk) (8.2.1-a2 or later)

All of these images are publicly available, and published on [Docker Hub](https://hub.docker.com/).

Expand Down
8 changes: 4 additions & 4 deletions docs/Install.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@
If you want to customize the installation of the Splunk Operator, download a copy of the installation YAML locally, and open it in your favorite editor.

```
wget -O splunk-operator.yaml https://github.com/splunk/splunk-operator/releases/download/1.0.1/splunk-operator-install.yaml
wget -O splunk-operator.yaml https://github.com/splunk/splunk-operator/releases/download/1.0.2/splunk-operator-install.yaml
```


Expand All @@ -18,13 +18,13 @@ Kubernetes only allows administrators to install new `CustomResourceDefinition`
If you are not an administrator, you can have an administrator create the required objects for you by running:

```
kubectl apply -f https://github.com/splunk/splunk-operator/releases/download/1.0.1/splunk-operator-crds.yaml
kubectl apply -f https://github.com/splunk/splunk-operator/releases/download/1.0.2/splunk-operator-crds.yaml
```

Afterwards, you can download and use the yaml file to install the operator within your own namespace:

```
wget -O splunk-operator.yaml https://github.com/splunk/splunk-operator/releases/download/1.0.1/splunk-operator-noadmin.yaml
wget -O splunk-operator.yaml https://github.com/splunk/splunk-operator/releases/download/1.0.2/splunk-operator-noadmin.yaml
kubectl config set-context --current --namespace=<NAMESPACE>
kubectl apply -f splunk-operator.yaml
```
Expand All @@ -35,7 +35,7 @@ kubectl apply -f splunk-operator.yaml
If you want to configure a single instance of the operator to watch all the namespaces of your cluster while managing deployments only in the namespace `splunk-operator`, use the alternative cluster scope installation yaml file:

```
wget -O splunk-operator.yaml https://github.com/splunk/splunk-operator/releases/download/1.0.1/splunk-operator-cluster.yaml
wget -O splunk-operator.yaml https://github.com/splunk/splunk-operator/releases/download/1.0.2/splunk-operator-cluster.yaml
```

**Note**: The operator has the ability to watch, list secret objects in all namespaces.
Expand Down
2 changes: 1 addition & 1 deletion docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -109,7 +109,7 @@ For production environments, we are requiring the use of Splunk SmartStore. As a

A Kubernetes cluster administrator can install and start the Splunk Operator by running:
```
kubectl apply -f https://github.com/splunk/splunk-operator/releases/download/1.0.1/splunk-operator-install.yaml
kubectl apply -f https://github.com/splunk/splunk-operator/releases/download/1.0.2/splunk-operator-install.yaml
```

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.
Expand Down
2 changes: 1 addition & 1 deletion docs/SplunkOperatorUpgrade.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ A Splunk Operator for Kubernetes upgrade might include support for a later versi
1. Download the latest Splunk Operator installation yaml file.
```
wget -O splunk-operator.yaml https://github.com/splunk/splunk-operator/releases/download/1.0.1/splunk-operator-install.yaml
wget -O splunk-operator.yaml https://github.com/splunk/splunk-operator/releases/download/1.0.2/splunk-operator-install.yaml
```
2. (Optional) Review the file and update it with your specific customizations used during your install.
Expand Down