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

versioning:bugfix - updating versioning files #136

Merged
merged 1 commit into from
Dec 17, 2021
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
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ Install Horusec-Operator on your cluster, see an example below:
1. Run the command:

```bash
kubectl apply -k "https://github.com/ZupIT/horusec-operator/config/default?ref=v2.2.1"
kubectl apply -k "https://github.com/ZupIT/horusec-operator/config/default?ref=v2.2.2"
```
2. Check if the resource was installed:
```bash
Expand Down Expand Up @@ -145,7 +145,7 @@ Don't worry, this is normal because the script is trying to create new database,

**Step 3.** After the script finishes, install Horusec-Operator:
```bash
kubectl apply -k "https://github.com/ZupIT/horusec-operator/config/default?ref=v2.2.1"
kubectl apply -k "https://github.com/ZupIT/horusec-operator/config/default?ref=v2.2.2"
```

**Step 4.** Check if the resource was installed:
Expand Down
2 changes: 1 addition & 1 deletion config/manager/kustomization.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -27,4 +27,4 @@ kind: Kustomization
images:
- name: controller
newName: horuszup/horusec-operator
newTag: v2.2.1
newTag: v2.2.2