Skip to content

🐛 ROSA: Add instructions to activate a newly created service account #5358

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

Jump to bottom
Merged
merged 1 commit into from
Mar 4, 2025
Merged

🐛 ROSA: Add instructions to activate a newly created service account #5358

merged 1 commit into from
Mar 4, 2025

Conversation

@mzazrivec
Copy link
Contributor

@mzazrivec mzazrivec commented Feb 18, 2025 •
edited
Loading

What type of PR is this?

/kind bug

What this PR does / why we need it:

This pull request adds another paragraph to ROSA installation guide, instructing our users to activate every newly created service account.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Checklist:

  • squashed commits
  • includes documentation
  • includes emoji in title
  • adds unit tests
  • adds or updates e2e tests

Release note:

@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-priority needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Feb 18, 2025
@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Feb 18, 2025

Hi @mzazrivec. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@mzazrivec mzazrivec changed the title ROSA: Add instructions to activate a newly created service account 🐛 ROSA: Add instructions to activate a newly created service account Feb 18, 2025
@mzazrivec mzazrivec changed the title 🐛 ROSA: Add instructions to activate a newly created service account 🐛 ROSA: Add instructions to activate a newly created service account Feb 18, 2025
serngawy
serngawy reviewed Feb 18, 2025
View reviewed changes
docs/book/src/topics/rosa/creating-a-cluster.md Outdated
CAPA controller requires service account credentials to be able to provision ROSA clusters:
1. Visit [https://console.redhat.com/iam/service-accounts](https://console.redhat.com/iam/service-accounts) and create a new service account.

1. For every newly created service account, make sure to activate the account using the [ROSA command line tool](https://github.com/openshift/rosa). First, log in using your newly created service account
Copy link
Contributor

@serngawy serngawy Feb 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

better to be a sub item or note for the previous step.

Copy link
Contributor Author

@mzazrivec mzazrivec Feb 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.

docs/book/src/topics/rosa/creating-a-cluster.md Outdated
## Permissions
### Authentication using service account credentials
CAPA controller requires service account credentials to be able to provision ROSA clusters:
1. Visit [https://console.redhat.com/iam/service-accounts](https://console.redhat.com/iam/service-accounts) and create a new service account.
Copy link
Contributor

@serngawy serngawy Feb 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
1. Visit [https://console.redhat.com/iam/service-accounts](https://console.redhat.com/iam/service-accounts) and create a new service account.
1. Visit [https://console.redhat.com/iam/service-accounts](https://console.redhat.com/iam/service-accounts) and create a service account. If you already have service account skip this step.

Copy link
Contributor Author

@mzazrivec mzazrivec Feb 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.

@serngawy
Copy link
Contributor

serngawy commented Feb 18, 2025

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Feb 18, 2025
@mzazrivec mzazrivec force-pushed the update_service_acct_doc_for_rosa branch from eb0be59 to e33ad1e Compare February 19, 2025 14:00
@k8s-ci-robot k8s-ci-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Feb 19, 2025
serngawy
serngawy approved these changes Feb 19, 2025
View reviewed changes
Copy link
Contributor

@serngawy serngawy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 19, 2025
@serngawy
Copy link
Contributor

serngawy commented Feb 20, 2025

@mzazrivec please update the release note; None or Update ROSA doc

@mzazrivec
Copy link
Contributor Author

mzazrivec commented Feb 20, 2025

/release-note-none

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Feb 20, 2025
damdo
damdo reviewed Feb 21, 2025
View reviewed changes
Copy link
Member

@damdo damdo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

/assign @AndiDog @dlipovetsky

For approval

@damdo damdo added the area/provider/rosa Issues or PRs related to Red Hat ROSA provider label Mar 4, 2025
@nrb
Copy link
Contributor

nrb commented Mar 4, 2025

/approve

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Mar 4, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nrb

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 4, 2025
@k8s-ci-robot k8s-ci-robot merged commit 777e8de into kubernetes-sigs:main Mar 4, 2025
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@damdo damdo damdo left review comments

@richardcase richardcase Awaiting requested review from richardcase

+1 more reviewer

@serngawy serngawy serngawy approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@nrb nrb

@serngawy serngawy

@AndiDog AndiDog

@dlipovetsky dlipovetsky

@damdo damdo

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/provider/rosa Issues or PRs related to Red Hat ROSA provider cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/bug Categorizes issue or PR as related to a bug. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesn't merit a release note. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

7 participants

@mzazrivec @k8s-ci-robot @serngawy @nrb @damdo @AndiDog @dlipovetsky