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

Jump to bottom

pod belong to deployment #4430

Open
showjason opened this issue Nov 9, 2021 · 3 comments
Open

pod belong to deployment #4430

showjason opened this issue Nov 9, 2021 · 3 comments
Assignees
@hzliangbin
Labels
good first issue help wanted kind/bug

Comments

@showjason
Copy link

@showjason showjason commented Nov 9, 2021 •
edited
Loading

Recently, I installed kubesphere in my own kubernetes cluster, deployed two deployments, each of them was setted one replica, they are different names, but the same selector and same template.Two pods was created, as kubernetes, these two pods should belong to different deployments, but as you can see as below screenshot, these two pods are belonging to the same deployment. I think the comparison between the name of pod and name of rs or deployment shoud be taken into consideration, not only the selector and hash value of template.
image

Versions Used
KubeSphere: v3.1.1
Kubernetes: v1.21.2

Environment
How many nodes and their hardware configuration:

For example: CentOS 7.9 / 1 masters: 4cpu/16g; 2 nodes: 8cpu/32g
(and other info are welcomed to help us debugging)

How To Reproduce
Steps to reproduce the behavior:

  1. Deploy two deployments that they are different names, but the same selector and same template
@RolandMa1986
Copy link
Member

@RolandMa1986 RolandMa1986 commented Nov 11, 2021

/kind bug
/good-first-issue

Loading

@ks-ci-bot
Copy link
Collaborator

@ks-ci-bot ks-ci-bot commented Nov 11, 2021

@RolandMa1986:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/kind bug
/good-first-issue

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/test-infra repository.

Loading

@hzliangbin
Copy link

@hzliangbin hzliangbin commented Nov 15, 2021

/assign

Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hzliangbin hzliangbin

Labels
good first issue help wanted kind/bug
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
@RolandMa1986 @hzliangbin @showjason @ks-ci-bot