[Policy Assistant] Cut the first release

[huntergregory]

EDIT 2: release complete: https://github.com/kubernetes-sigs/network-policy-api/releases/tag/v0.0.1-policy-assistant

EDIT: we are going to use policy-assistant instead of pola per #262

Perhaps we can cut a release just for policy assistant, called v0.0.1-pola? Looks like there are no overlapping or bad connotations for this POLA abbreviation from my Google search 😅

Requirements

• CI/CD:
  • [Policy Assistant] use internal vendoring instead of vendoring from Cyclonus #170
  • [Policy Assistant] update binary names to policy-assistant instead of cyclonus #254
  • ci: [Policy Assistant] tests in github action #246
  • cut release
• features:
  • feat: [Policy Assistant] walkthrough mode and a README (KubeCon demo PR 2/2) #245
  • [Policy Assistant] user experience for specifying pods/traffic #220

Nice to have

• [Policy Assistant] remove support for SameLabels and NotSameLabels #212:
  • added warning in fix: [Policy Assistant] warn that SameLabels and NotSameLabels are deprecated #261
• [Policy Assistant] Remove Cyclonus Code which isn't needed #151
  • removed unimplemented CLI args per feat: [Policy Assistant] walkthrough mode and a README (KubeCon demo PR 2/2) #245

[huntergregory]

EDIT: we are going to use policy-assistant instead of pola per #262

Discussed cutting a v0.0.1-pola release for the pola CLI in last week's meeting. We will target a release date of November 5th

[huntergregory]

EDIT: rename pola to policy-assistant per #262

Discussed tying policy-assistant version to the API version used. Discussed how the first release might not follow that format though.

Two ideas for first release:

• idea 1: v0.0.1-policy-assistant
• idea 2: v0.1.1-policy-assistant-20241105
  • <api-version-used>-policy-assistant-<date>

[npinaeva]

One question I have is do we plan to support multiple API versions with the same binary? It sounds like it could be useful to not reinstall the binary if you have 2 clusters with different ANP versions. In that case the tool could have its own versions, just adding support for newer API versions as it progresses?

[huntergregory]

One question I have is do we plan to support multiple API versions with the same binary? It sounds like it could be useful to not reinstall the binary if you have 2 clusters with different ANP versions. In that case the tool could have its own versions, just adding support for newer API versions as it progresses?

After revisiting this question, I'm not sure we can support multiple API versions in the same CLI: https://stackoverflow.com/questions/63254746/how-to-import-two-versions-of-the-same-go-module

[huntergregory]

release complete: https://github.com/kubernetes-sigs/network-policy-api/releases/tag/v0.0.1-policy-assistant