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

Use different user #11959

Closed
Silvanoc opened this issue Jul 8, 2021 · 7 comments
Closed

Use different user #11959

Silvanoc opened this issue Jul 8, 2021 · 7 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@Silvanoc
Copy link

Silvanoc commented Jul 8, 2021

/kind feature

In my company we have an IAM system that can be used in parallel to the AWS one and provides additional functionality. But I'm not free to select whatever user I want.

Is there a technical reason why I cannot use the username that I like and I'm being forced to create a kops user? Or is it simply a missing feature?

In my case I can use different roles to specify different policies and that's what I'd do for kOps.
I'd simply need an optional argument like --username.

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Jul 8, 2021
@olemarkus
Copy link
Member

I don't quite follow what you want from this request. Where does kOps require a user called kops? Are you referring to the IAM user from the example docs? If so, that is just an example. You can run kOps from any environment that has the sufficient privileges.

@Silvanoc
Copy link
Author

Silvanoc commented Jul 9, 2021

When I've seen "The kops user", I've interpreted that the users name HAS to be kops. I mean, you have a bit afterwards the sentence "... the kOps IAM user", what is obvious enough not to be a username.

If whatever user with the right permissions works, then the origin of my error must be something else 🙂 and this issue can be closed. I was wondering anyway, why you need a specific user. But I didn't know how to ask it otherwise since there's no Slack, Google Groups or similar.

May I then propose to add an explanation sentence like "Whatever user with the required permissions will suffice, we will use kops in the following code snippets."? Or replacing the sample user with kops_user, john_doe,...

@olemarkus
Copy link
Member

#kops-user channel on the k8s slack :)

@Silvanoc
Copy link
Author

Silvanoc commented Jul 9, 2021

Having the discussion now here, I won't reopen it in Slack 🙂

Since I assume that my previous comment is correct (whatever user with specified permissions will suffice) because you didn't correct it, I'm closing this issue.

Thanks for your quick reaction and great tool.

@Silvanoc Silvanoc closed this as completed Jul 9, 2021
@Silvanoc
Copy link
Author

Silvanoc commented Jul 9, 2021

BTW @olemarkus just a heads-up regarding the Slack channel and contribution documentation.

The document CONTRIBUTING.md doesn't report neither the Slack channel nor the contribution documentation.

The contribution documentation is returning me 404.

I've only be able to confirm that you provide the Slack channel in the contribution documentation doing a GitHub search on your repo.

@moshevayner
Copy link
Member

BTW @olemarkus just a heads-up regarding the Slack channel and contribution documentation.

The document CONTRIBUTING.md doesn't report neither the Slack channel nor the contribution documentation.

The contribution documentation is returning me 404.

I've only be able to confirm that you provide the Slack channel in the contribution documentation doing a GitHub search on your repo.

@Silvanoc thanks for raising the flag on that!
Regarding the Slack channels, you can see their info here.
And regarding the broken link, I have created PR #11979 to fix it, it should be pointing here instead.

@Silvanoc
Copy link
Author

Regarding the Slack channels, you can see their info here.

I found the info looking searching for it in the code of this repo, but I nevertheless would expect CONTRIBUTING.md to provide the link https://kops.sigs.k8s.io/contributing/ or to mention it (if no link is desired to a possibly changing documentation page) like "look at the docs to contact the community".

And regarding the broken link, I have created PR #11979 to fix it, it should be pointing here instead.

It appears to be working now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

4 participants