search

kubernetes-sigs / network-policy-api

This repo addresses further work involving Kubernetes network security beyond the initial NetworkPolicy resource
Apache License 2.0
50 stars 28 forks source link

[Policy Assistant] update binary names to policy-assistant instead of cyclonus #171

Closed huntergregory closed 1 week ago

huntergregory commented 8 months ago

Related to #150.

See https://github.com/kubernetes-sigs/network-policy-api/pull/159#discussion_r1375079221.

Peac36 commented 5 months ago

/assign

Peac36 commented 5 months ago

Hey @huntergregory, should I also change the tag that is used during the building of the docker image?

huntergregory commented 5 months ago

Assuming the question's about image tags. I'd suggest we create a new docker image called policy-assistant:v0.0.1. We should probably establish a release process for creating new tags.

Peac36 commented 5 months ago

What about the docker repo(docker.io/mfenwick100)? Should we continue to use that one or switch to k8s-related repo?

huntergregory commented 5 months ago

Ideally a k8s-related one. @astoycos do you know a repo we could use?

k8s-triage-robot commented 2 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 1 month ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 1 week ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 1 week ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes-sigs/network-policy-api/issues/171#issuecomment-2197530713): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
huntergregory commented 1 week ago

/remove-lifecycle rotten

huntergregory commented 1 week ago

/open