feat (extensions) : Add DSL for Open Virtual Networking k8s.ovn.org API group resources

[rohanKanojia]

Description

Fix #5636

Add OpenVirtualNetworkingClient with entrypoint v1() which will expose the following resources:

• ovnClient.v1().egressIps()
• ovnClient.v1().egressQoses()
• ovnClient.v1().egressFirewalls()
• ovnClient.v1().egressServices()
• ovnClient.v1().adminPolicyBasedExternalRoutes()

User would need to add this dependency in order to use this extension:

    <dependency>
      <groupId>io.fabric8</groupId>
      <artifactId>open-virtual-networking-client</artifactId>
      <version>${fabric8.version}</version>
    </dependency>

Here is an example of sample usage:

    try (OpenVirtualNetworkingClient ovnClient = new KubernetesClientBuilder().build().adapt(OpenVirtualNetworkingClient.class)) {
      EgressFirewall egressFirewall = new EgressFirewallBuilder()
          .withNewMetadata()
          .withName("default")
          // ...
          .build();
      egressFirewall = ovnClient.v1().egressFirewalls().resource(egressFirewall).serverSideApply();

      egressFirewall = ovnClient.v1().egressFirewalls().resource(egressFirewall).get();
      System.out.println(egressFirewall.getMetadata().getName() + " Created");
    }

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change
• Chore (non-breaking change which doesn't affect codebase;
  test, version modification, documentation, etc.)

Checklist

• Code contributed by me aligns with current project license: Apache 2.0
• I Added CHANGELOG entry regarding this change
• I have implemented unit tests to cover my changes
• I have added/updated the javadocs and other documentation accordingly
• No new bugs, code smells, etc. in SonarCloud report
• I tested my code in Kubernetes
• I tested my code in OpenShift

[manusa]

Overall looks good.
However, I don't understand why the model is in kubernetes-model-ovn while the DSL is declared in the OpenShiftClient

[rohanKanojia]

I named the module kubernetes-model-ovn because of k8s.ovn.org API group. These resources are CRDs that are not available in vanilla Kubernetes Clusters.

User requested to add DSL in openshift client in #5636 (comment). We can also have it as an extension.

[manusa]

User requested to add DSL in openshift client in #5636 (comment). We can also have it as an extension.

I understand the user requested it in the scope of the OpenShift recommendation. However, these resources aren't exclusive to OpenShift, it would be weird to have a Kubernetes Cluster with OVN enabled and having to access this API through client.adapt(OpenShiftClient.class) plus requiring the OpenShift client module.

For me it's either making it accessible through the standard KubernetesClient DSL or creating an extension.

[rohanKanojia]

I would prefer having it as an extension. If you agree I can create PR to migrate model to extensions/

[sonarqubecloud]

Quality Gate failed

Failed conditions

52.2% Coverage on New Code (required ≥ 80%)

See analysis details on SonarCloud