Support new API version for ClientIntents: v2beta1

[omris94]

Description

We have revamped the format for ClientIntents to make them easier to understand and make it possible to generate more restrictive policies by default. Read more on the docs >>

The two primary changes is that the word service is no longer used, except to mean a Kubernetes Service; before, it could mean an Otterize Service or a Kubernetes Service, which was confusing. Instead, we now use workload . calls have also been renamed targets , and many smaller changes to the structure to improve

What happens to your existing ClientIntents? Don’t worry, the change is backwards compatible, and nothing changes unless you explicitly upgrade. If you’re a customer, we’ll reach out to explain and plan together. If you’re using the open source, upgrading to the next major version of the otterize-kubernetes Helm chart, vX.X.X will make ClientIntents v2 the default. You can still continue applying ClientIntents with apiVersion v1alpha3, and they will be converted by the Intents Operator to v2beta1.

References

otterize/intents-operator#552
#179
otterize/network-mapper#267
otterize/helm-charts#278

Testing

• This change adds test coverage for new/changed/fixed functionality

Checklist

• I have added documentation for new/changed functionality in this PR and in github.com/otterize/docs