Create OpenAPI Kubernetes client integration with OKE

[andriy-dmytruk]

Integration the OpenAPI Kubernetes client with OKE that adds:

• OkeKubeConfigLoader that loads kubeconfig from a specified cluster with the OCI Container Engine client.
• OkeKuberenetesCredentialLoader that provides token for OKE server requests. The tokens are based on the OCI AuthenticationDetailsProvider

[github-actions]

❌ Oracle Cloud CI 17 latest failed: https://ge.micronaut.io/s/trxptrkgnqtwc

[github-actions]

❌ Oracle Cloud CI 17 latest failed: https://ge.micronaut.io/s/ajgx6bmyofemw

[andriy-dmytruk]

Strange, it says region provider is missing. But it should not be required if endpoint was set explicitly. I don't even see RegionProvider injected in the ContainerEngineClientFactory.

Path Taken: new KubernetesHttpClientFactory(KubeConfigLoader kubeConfigLoader,KubernetesClientConfiguration kubernetesClientConfiguration,KubernetesPrivateKeyLoader kubernetesPrivateKeyLoader,ResourceResolver resourceResolver,DefaultHttpClientFilterResolver defaultHttpClientFilterResolver) --> new KubernetesHttpClientFactory([KubeConfigLoader kubeConfigLoader],KubernetesClientConfiguration kubernetesClientConfiguration,KubernetesPrivateKeyLoader kubernetesPrivateKeyLoader,ResourceResolver resourceResolver,DefaultHttpClientFilterResolver defaultHttpClientFilterResolver) --> new OkeKubeConfigLoader([ContainerEngineClient containerEngineClient],OkeKubernetesClientConfig config,ResourceResolver resourceResolver) --> ContainerEngineClientFactory.build(Builder clientBuilder,AbstractAuthenticationDetailsProvider authenticationDetailsProvider,[RegionProvider regionProvider])

[andriy-dmytruk]

@n0tl3ss Unfortunately it seems like #1040 is breaking this.

[github-actions]

❌ Oracle Cloud CI 17 latest failed: https://ge.micronaut.io/s/yu7mwl3epdbqq

[sonarqubecloud]

Quality Gate failed

Failed conditions
1 New Bugs (required ≤ 0)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

[n0tl3ss]

The sonar reports that volatile isn't enough for thread safe code.

[andriy-dmytruk]

The sonar reports that volatile isn't enough for thread safe code.

I copied the volatile part from our openapi kubernetes client credential loader implementation. I think it fine, as implementation only uses volatile when getting the token. When it needs to set the token, it uses a synchronized block.