Support for Network Policies

[FlorianOtel]

Hello all,

As described in this thread, I've discovered that the existing "client-go" package does not yet support extension methods for network policies.

By modelling it after existing support for PodSecurityPolicy -- and some help from the main repository -- I have now implemented those methods.

They are located in my fork here: https://github.com/FlorianOtel/client-go

However, it seems that any PRs have to be submitted via main repo, as opposed to directly here.

Unless otherwise advised, I will try doing so next.

Submitting this issue here for reference.

Thanks,

/Florian

[caesarxuchao]

Hi Florian, the reason NetworkPolicy is missing in the client-go is because this tag is missing in the pkg/apis/extensions/v1beta1/types.go.

To fix it, in the main repo,

1. add the // +genclient=true to pkg/apis/extensions/v1beta1/types.go.
2. run hack/update-codegen.sh
3. run hack/update-staging-client-go.sh

After the PR gets merged, the changes will be populated to client-go in 24 hours.

[FlorianOtel]

Hi,

Kindest thanks for the guidance, much appreciated -- esp. considering this is my first K8S PR :)

I've submitted the pull request already -- it's PR #39155

Thanks,

/Florian

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close