Feat: Adding hostAliases in PodTemplate spec.

[xclud]

Changes

Adding hostAliases in PodTemplate spec.

/kind feature

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

• Docs included if any changes are user facing
• Tests included if any functionality added or changed
• Follows the commit message standard
• Meets the Tekton contributor standards (including
  functionality, content, code)
• Release notes block below has been filled in or deleted (only if no user facing changes)

Release Notes

Feat: Add hostAliases in PodTemplate spec which provides Pod-level override of hostname resolution by modifing /etc/hosts.

[tekton-robot]

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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

[ghost]

Thanks a lot for tackling this!

[ghost]

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.

[xclud]

I made the changes and removed them. However, volumes field has patchStrategy and patchMergeKey, just to say.

[ghost]

Ah, you are right, thanks for pointing that out - I missed volumes when i looked!

[ghost]

/ok-to-test

[xclud]

/retest

[ghost]

@xclud you'll need to run ./hack/update-openapigen.sh I think to generate the open api changes. Also please squash commits down into 1 🙏

Re-running integration tests:

/test pull-tekton-pipeline-integration-tests

[xclud]

@sbwsg I donno how to squash commits in github (i am from gitlab background). Would you please help?

[ghost]

@sbwsg I donno how to squash commits in github (i am from gitlab background). Would you please help?

Sure, although I'm only from git-land so I only know the CLI command :D

1. Run git rebase -i HEAD^^^^
2. This will give you an editor window with the list of commits in your branch
3. Change all entries after the first in the list of commits so that they start with f . This means "fixup" which will result in all the commits after your first one being squashed together. It will also discard the commit message associated with each of the commits (except for your first one). If you want to keep the commit messages from those then use s instead of f .
4. Save and quit the editor

Now when you git show HEAD you should see that all your changes appear in a single commit. git log should now show just a single commit on top of whatever the branch had before.

[ghost]

Oh, almost forgot - after you do this and confirm that everything looks correct you'll need to force push to your remote branch with git push --force <your remote> <your branch>

[ghost]

The build tests are failing because ./hack/update-openapigen.sh has generated diffs that look like this:

-	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 GOPATH. We've got an issue open to tackle this here: #3884

@xclud can you try re-running ./hack/update-openapigen.sh from within your GOPATH to see if that correctly writes these Refs? One way to do this (according to that issue) is to symlink your Pipeline working directory to $GOPATH/src/github.com/tektoncd/pipeline 🤞

[ghost]

Oh no! I wrote update-codegen.sh when I should have written update-openapigen.sh Apologies! I'll update that previous comment.

[linux-foundation-easycla]

The committers are authorized under a signed CLA.

• ✅ Mahdi (3bb7ec5)

[pritidesai]

Thank you @xclud for your contributions, changes look great 🙏

The build is failing with:

/home/prow/go/src/github.com/tektoncd/pipeline is out of date. Please run hack/update-codegen.sh

Please rerun the update-codegen.sh and hopefully it works for you.

@sbwsg awesome instructions on squashing the commits. 👍

[xclud]

Thank you @xclud for your contributions, changes look great 🙏

The build is failing with:

/home/prow/go/src/github.com/tektoncd/pipeline is out of date. Please run hack/update-codegen.sh

Please rerun the update-codegen.sh and hopefully it works for you.

@sbwsg awesome instructions on squashing the commits. 👍

I already ran update-codegen.sh. It only updates my go.sum file. Should i push it as well ?

[ghost]

I don't quite know why but the order of Dependencies in the generated openapi_generated.go file is changing. Notice below how pod.Template shifts position in the list.

 		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 go version? @xclud what version are you running?

I think the quickest way to get this resolved would be to hand-edit openapi_generated.go locally and move "github.com/tektoncd/pipeline/pkg/apis/pipeline/pod.Template" in those two lists to match the expectation of the test runner. Really sorry about that, it's not a great dev experience but hopefully it resolves the immediate problem.

[pritidesai]

Yay, the build is passing 🎉

There is an ongoing issue with integration test, not related to your changes, see @sbwsg's comment on another PR.

[pritidesai]

@xclud one last thing, please add some details in commit message, it's easier for folks later to understand the changes. 🙏

[xclud]

@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.

[xclud]

@xclud one last thing, please add some details in commit message, it's easier for folks later to understand the changes. 🙏

I am messing up with git :D sorry guys. I try to fix it.

[xclud]

@sbwsg I tried to push a message-only commit and squash. Now i see all my changes are gone. I am stuck.

[ghost]

@xclud no worries; here are some git commands to rescue the changes:

1. Make sure you're on your branch
2. Run git reset --hard 00f3b3a
3. This should put you back in a good state with the code (back to here)
4. Run git commit --amend
5. This should show you a screen to edit the commit message.
6. Make edits and save.
7. git push --force <remote name> <branch name>

[tekton-robot]

[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:

• OWNERS [sbwsg]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[xclud]

@sbwsg Thanks again. I also updated the release notes.

[ghost]

@sbwsg Thanks again. I also updated the release notes.

Great work, thanks a lot for sticking with it through this whole process!

[pritidesai]

thanks @sbwsg for very helpful git pointers 🎉

Great work, thanks a lot for sticking with it through this whole process!

yup, 💯 thank you @xclud 👍 and welcome to the community 🙏

/lgtm

hopefully, the changes will be merged after we fix the integration tests 🤞

[ghost]

You'll need to rebase on top of main to get the integration tests passing.

1. git fetch upstream
2. git rebase upstream/main
3. git push --force <your remote> <branch name>

[xclud]

@sbwsg Done. But it seems integration tests are still failing.

[vdemeester]

default 4m46s Normal VolumeDelete persistentvolume/pvc-03141f10-77ba-4fe2-9cfa-a29fcf067319 googleapi: Error 400: The disk resource 'projects/tekton-prow-9/zones/us-central1-b/disks/gke-tpipeline-e2e-cls1-pvc-03141f10-77ba-4fe2-9cfa-a29fcf067319' is already being used by 'projects/tekton-prow-9/zones/us-central1-b/instances/gke-tpipeline-e2e-cls138-default-pool-ed3cdb7a-hk83', resourceInUseByAnotherResource

Seems like too much rebuild happened at the same time 😓

/retest

[xclud]

/retest

[ghost]

/test pull-tekton-pipeline-integration-tests

[pritidesai]

/lgtm

[xclud]

Thank you guys. I am happy to see this PR is merged.

Can we also close #1750?

[pritidesai]

Can we also close #1750?

Yup, we can close #1750