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

Add inbuilt support for popular managed cloud kubernetes services #25

Closed
ashokponkumar opened this issue Oct 2, 2020 · 7 comments
Closed
Assignees
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. hacktoberfest help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

Comments

@ashokponkumar
Copy link
Member

The task involves the following:

  1. Setting up a terminal with the cluster in context for kubectl
  2. Run move2kube collect
  3. Copy the m2k_collect/clusters/
  4. Change name to .yaml
  5. In yaml, change metadata.name to clustername used above
  6. Check in to https://github.com/konveyor/move2kube/tree/master/internal/metadata/clusters
  7. Do make generate
  8. Submit a pull request after committing with git commit -s -m comment
@ashokponkumar ashokponkumar added good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. hacktoberfest labels Oct 2, 2020
@ashokponkumar
Copy link
Member Author

@akhil-ghatiki If you have access to any kubernetes cluster from any of the cloud services, this might be a easy issue to fix, in case you are interested.

@akhil-ghatiki
Copy link
Contributor

akhil-ghatiki commented Oct 13, 2020

I will check this out. I think I better work on this first than Add collector for Amazon ECS and Azure Container Service #43. (Because #43 is demanding some exploration)

@akhil-ghatiki
Copy link
Contributor

@ashokponkumar I have set up the terminal with the cluster in context for kubectl for an aws eks. After running the move2kube collect the cluster folder is just empty. No yml got generated.
Screenshot 2020-10-14 at 10 16 36 PM

Is there any other configuration that has to be changed ? OR I afraid if #43 has to be fixed before this can be fixed.

@ashokponkumar
Copy link
Member Author

@ashokponkumar I have set up the terminal with the cluster in context for kubectl for an aws eks. After running the move2kube collect the cluster folder is just empty. No yml got generated.
Screenshot 2020-10-14 at 10 16 36 PM

Is there any other configuration that has to be changed ? OR I afraid if #43 has to be fixed before this can be fixed.

@akhil-ghatiki #43 is about container service, and is not related to this issue. Can you please share the log output of move2kube collect -v?

@akhil-ghatiki
Copy link
Contributor

@ashokponkumar any more managed services support is required ? or is this issue good to close ?

@ashokponkumar
Copy link
Member Author

If you have access to managed openshift in any of them, we can use them too. If not, lets close it for now.

@akhil-ghatiki
Copy link
Contributor

If you have access to managed openshift in any of them, we can use them too. If not, lets close it for now.

I don't have the access to managed to openshift in them. I think now we can create an issue asking for specific inbuilt support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. hacktoberfest help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
Projects
None yet
Development

No branches or pull requests

2 participants