-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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: Adding hostAliases in PodTemplate spec. #3889
Conversation
Hi @xclud. Thanks for your PR. I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the 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/test-infra repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for tackling this!
pkg/apis/pipeline/pod/template.go
Outdated
// +optional | ||
// +patchMergeKey=ip | ||
// +patchStrategy=merge | ||
HostAliases []corev1.HostAlias `json:"hostAliases,omitempty" patchStrategy:"merge" patchMergeKey:"ip" protobuf:"bytes,23,rep,name=hostAliases"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think strategic merge patch is supported on CRDs. We also don't have patchStrategy
and patchMergeKey
on any other fields in this struct. Suggest removing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I made the changes and removed them. However, volumes
field has patchStrategy
and patchMergeKey
, just to say.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, you are right, thanks for pointing that out - I missed volumes when i looked!
/ok-to-test |
/retest |
@xclud you'll need to run Re-running integration tests: /test pull-tekton-pipeline-integration-tests |
@sbwsg I donno how to squash commits in github (i am from gitlab background). Would you please help? |
Sure, although I'm only from
Now when you |
Oh, almost forgot - after you do this and confirm that everything looks correct you'll need to force push to your remote branch with |
The build tests are failing because - Ref: ref("github.com/tektoncd/pipeline/pkg/apis/pipeline/v1beta1.TaskResult"),
+ Ref: ref("./pkg/apis/pipeline/v1beta1.TaskResult"), I asked in Slack and it sounds like the reason this happens is because the script is running outside of @xclud can you try re-running |
Oh no! I wrote |
|
Thank you @xclud for your contributions, changes look great 🙏 The build is failing with:
Please rerun the @sbwsg awesome instructions on squashing the commits. 👍 |
I already ran |
I don't quite know why but the order of Dependencies in the generated Dependencies: []string{
- "github.com/tektoncd/pipeline/pkg/apis/pipeline/pod.Template", "github.com/tektoncd/pipeline/pkg/apis/pipeline/v1beta1.Param", "github.com/tektoncd/pipeline/pkg/apis/pipeline/v1beta1.TaskRef", "github.com/tektoncd/pipeline/pkg/apis/pipeline/v1beta1.TaskRunResources", "github.com/tektoncd/pipeline/pkg/apis/pipeline/v1beta1.TaskSpec", "github.com/tektoncd/pipeline/pkg/apis/pipeline/v1beta1.WorkspaceBinding", "k8s.io/apimachinery/pkg/apis/meta/v1.Duration"},
+ "github.com/tektoncd/pipeline/pkg/apis/pipeline/v1beta1.Param", "github.com/tektoncd/pipeline/pkg/apis/pipeline/v1beta1.TaskRef", "github.com/tektoncd/pipeline/pkg/apis/pipeline/v1beta1.TaskRunResources", "github.com/tektoncd/pipeline/pkg/apis/pipeline/v1beta1.TaskSpec", "github.com/tektoncd/pipeline/pkg/apis/pipeline/v1beta1.WorkspaceBinding", "github.com/tektoncd/pipeline/pkg/apis/pipeline/pod.Template", "k8s.io/apimachinery/pkg/apis/meta/v1.Duration"},
} Very annoying! I wonder if this is related to I think the quickest way to get this resolved would be to hand-edit |
@xclud one last thing, please add some details in commit message, it's easier for folks later to understand the changes. 🙏 |
@sbwsg @pritidesai Thank you guys for your support. I appreciate it. I am from Windows background and git-clicks. I learned from you. I squashed the commits. |
I am messing up with git :D sorry guys. I try to fix it. |
@sbwsg I tried to push a message-only commit and squash. Now i see all my changes are gone. I am stuck. |
@xclud no worries; here are some git commands to rescue the changes:
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbwsg 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 |
@sbwsg Thanks again. I also updated the release notes. |
Great work, thanks a lot for sticking with it through this whole process! |
You'll need to rebase on top of
|
…of hostname resolution by modifing /etc/hosts.
@sbwsg Done. But it seems integration tests are still failing. |
Seems like too much rebuild happened at the same time 😓 /retest |
/retest |
/test pull-tekton-pipeline-integration-tests |
/lgtm |
Thank you guys. I am happy to see this PR is merged. Can we also close #1750? |
Changes
Adding hostAliases in PodTemplate spec.
/kind feature
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
Release Notes