Can JKube plugins can be bound to after the k8s:appply operation phases

[zhoujianhui]

Component

None

Is your enhancement related to a problem? Please describe

Can JKube plugins can be bound to after the k8s:appply operation phases?

Describe the solution you'd like

Can JKube plugins can be bound to after the k8s:appply operation phases

Describe alternatives you've considered

No response

Additional context

No response

[rohanKanojia]

@zhoujianhui : Sorry, I don't understand. Could you please elaborate? Are you talking about some specific goals?

[zhoujianhui]

yes, I want to perform additional operations through the JKube plugin after executing k8s:apply in the Kubernetes Maven plugin. However, the current plugin can only execute custom operations before k8s:build.

[manusa]

I guess this is more about Maven project configuration

The default phase for the apply goal is Install.

You have some information about Maven lifecycle phases here: https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html

You can add an <execution> configuration to your Maven plugin and add whatever you want there.

[zhoujianhui]

In this doc https://eclipse.dev/jkube/docs/kubernetes-maven-plugin/#jkube-plugin, it says "This plugin supports so call jkube-plugins which have entry points that can be bound to the different JKube operation phases".I just want to implement a jkube plugin perform additional operations after k8s:apply not before k8s:build.

[manusa]

OK, I understand now that you are talking about the JKube plugin interface and not about the JKube Maven plugin or Gradle plugin.

In this case, then no, at the moment the JKubePlugin interface only supports adding additional files to the build (as showcased in the docs and examples).

It would be good to understand what your use-case is so that maybe the interface can be enhanced to support it.

However, it's very likely that your use-case can be supported by specific maven plugins designed for this purpose.

The exec-maven-plugin is commonly used for this purpose https://www.mojohaus.org/exec-maven-plugin/

[zhoujianhui]

The concept of "Projects" in Rancher clusters does not exist in native Kubernetes. Therefore, when using the kubernetes-maven-plugin to create a namespace, it's not possible to specify the associated Rancher project.

After the namespace is created, it will appear under the "Default" project by default. At this point, you can either move the namespace to the desired project manually or associate it with a project using the “field.cattle.io/projectId” annotation. However, note that when using the f“field.cattle.io/projectId” annotation, the namespace will not be deleted automatically when the associated project is deleted.

I want to move the namespace to a specific project after creation using the JKube plugin, but currently the required API support is incomplete.