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

Feat (dev env): allow to custom registry port for make kind-up #1417

Merged
merged 3 commits into from
Nov 16, 2022

Conversation

zou8944
Copy link
Contributor

@zou8944 zou8944 commented Oct 31, 2022

Type of change:

  • New feature provided

What this PR does / why we need it:

#1416

Pre-submission checklist:

  • Did you explain what problem does this PR solve? Or what new features have been added?
  • Have you added corresponding test cases?
  • Have you modified the corresponding document?
  • Is this PR backward compatible? If it is not backward compatible, please discuss on the mailing list first

@zou8944 zou8944 changed the title Draft: allow to custom registry port for make kind-up feat: allow to custom registry port for make kind-up Oct 31, 2022
@tao12345666333 tao12345666333 changed the title feat: allow to custom registry port for make kind-up Feat (dev env): allow to custom registry port for make kind-up Nov 1, 2022
@tao12345666333 tao12345666333 added this to the v1.6.0 milestone Nov 1, 2022
@tao12345666333 tao12345666333 linked an issue Nov 1, 2022 that may be closed by this pull request
@@ -67,7 +67,7 @@ nodes:
containerdConfigPatches:
- |-
[plugins."io.containerd.grpc.v1.cri".registry.mirrors."localhost:${reg_port}"]
endpoint = ["http://${reg_host}:${reg_port}"]
endpoint = ["http://${reg_host}:5000"]
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hi, @tao12345666333 @lingsamuel , I update this port, it should be fixed 5000 port.

Copy link
Member

Choose a reason for hiding this comment

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

Hi, @tao12345666333 @lingsamuel , I update this port, it should be fixed 5000 port.

why it should be 5000?

Copy link
Contributor Author

@zou8944 zou8944 Nov 10, 2022

Choose a reason for hiding this comment

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

@tao12345666333 the endpoint will be visit by k8s node which kind created, so the port should be the one that registry exposed (which is 5000 fixed), not the one that registry published on our local machine.
you can also refer to the kind doc, and pay attention to this part
image

Copy link
Member

Choose a reason for hiding this comment

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

okay, I miss it.

@zou8944
Copy link
Contributor Author

zou8944 commented Nov 3, 2022

@tao12345666333 @lingsamuel , New commit updated, please review, thanks.

@tao12345666333 tao12345666333 merged commit 6ec804f into apache:master Nov 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

Successfully merging this pull request may close these issues.

feat: allow to custom port when make kind-up
3 participants