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

[RELEASE] Operator v5.0.0 #791

Closed
8 tasks done
djwfyi opened this issue Mar 30, 2023 · 0 comments · Fixed by #838
Closed
8 tasks done

[RELEASE] Operator v5.0.0 #791

djwfyi opened this issue Mar 30, 2023 · 0 comments · Fixed by #838
Assignees

Comments

@djwfyi
Copy link
Collaborator

djwfyi commented Mar 30, 2023

Operator v5.0.0 has changes that impact the docs:

  • Now supports Workload identities for KES + GKE (PR #1501)

  • Creates operator environment variables (PR #1518)

  • TLS moved from operator to the sidecar (PR #1515)
    - see also the updated Operator TLS docs as changed in PR #1473

  • Generate and download tenant reports (PR #1498)

  • Operator now utilizes separate initContainer and sidecar containers (PR #1437)

  • Additional support for Openshift for the kubectl proxy command (PR #1431)

  • New tenants now have the audit logs and prometheus disabled by default (this deprecation was previously announced) (PR #1433)

  • Operator 5.0.2 added documentation for how to continue using prometheus and audit logs after upgrading (PR #1525)

@djwfyi djwfyi self-assigned this Apr 24, 2023
djwfyi added a commit that referenced this issue Apr 27, 2023
djwfyi added a commit that referenced this issue Apr 28, 2023
Updates docs for most changes through v5.0.4.
Does not have changes related to sidecar containers.

Partially addresses #791

Staged: http://192.241.195.202:9000/staging/operator-5.0.0/index.html
djwfyi added a commit that referenced this issue May 5, 2023
This adds information about Operator component changes in v5.0.x.

Closes #791 

Staged:
http://192.241.195.202:9000/staging/operator-sidecar/operations/installation.html
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant