This channel is for discussions related to Eclipse JKube, successor of Fabric8 Maven Plugin.
Windows 11 using the intellij ultimate edition
Also could you recommend some good first issues ?
I have been working in java for more than a year now but I haven't worked on a big project
You can check out the project and create issue for anything you think needs to change.
HI @Mohd-Farhan , we'll be creating new Hacktoberfest issues from Monday to Friday throughout the month. Please be sure to check regularly the Hacktoberfest label https://github.com/eclipse/jkube/labels/Hacktoberfest
Also note that only new contributors are elegible for these issues, and that they can only choose one.
Also note that only new contributors are elegible for these issues, and that they can only choose one.
Hello to everyone,
I have a question regarding the kubernetes-maven-plugin in zero config mode. I would like to use the Git commit id as tag for the image name. But when I use e.g. <jkube.generator.name>registry.gitlab.com/myspace/myproject/testcontainer:${git.commit.id.abbrev}</jkube.generator.name> where ${git.commit.id.abbrev} comes from the pl.project13.maven:git-commit-id-plugin, I got an error "Given Docker name ... is invalid". I tried with ${project.version} and with system properties given with -D on command line, both worked.
I looked into the code and found in org.eclipse.jkube.generator.api.support.BaseGenerator that the properties loaded by this call Configs.getFromSystemPropertyWithPropertiesAsFallback(getProject().getProperties(), ..). I tried to find out how JavaProject#getProperties is initialized and maybe find out why the properties created by the git-commit-id-plugin are not recognized, but my maven plugin understanding seems not enough at this point.
Might this be an issue, feature request or do I miss something?
I have a question regarding the kubernetes-maven-plugin in zero config mode. I would like to use the Git commit id as tag for the image name. But when I use e.g. <jkube.generator.name>registry.gitlab.com/myspace/myproject/testcontainer:${git.commit.id.abbrev}</jkube.generator.name> where ${git.commit.id.abbrev} comes from the pl.project13.maven:git-commit-id-plugin, I got an error "Given Docker name ... is invalid". I tried with ${project.version} and with system properties given with -D on command line, both worked.
I looked into the code and found in org.eclipse.jkube.generator.api.support.BaseGenerator that the properties loaded by this call Configs.getFromSystemPropertyWithPropertiesAsFallback(getProject().getProperties(), ..). I tried to find out how JavaProject#getProperties is initialized and maybe find out why the properties created by the git-commit-id-plugin are not recognized, but my maven plugin understanding seems not enough at this point.
Might this be an issue, feature request or do I miss something?
17 replies
I want to contribute in the project but I don't find good first issue, so can anyone create them?
@rohanKanojia and @manusa can you please review the preview of our final work submission?
https://gist.github.com/anurag-rajawat/a4c5f26e1c85deccd5742f614271475d
https://gist.github.com/anurag-rajawat/a4c5f26e1c85deccd5742f614271475d
and how to change owner of folder in container suppose /var/log/Application to 1000 i.e jboss
how to change ownership of a mount directory and how to give 777 permission to mount directory
can you please show a demo project for jkube host and local volume
i have done all but i get permission issue for mount directories
Hi, I think we communicated on email. Here are examples of host path and local volumes:
Host path: https://github.com/rohankanojia-forks/jkube-testing/tree/main/jkube-hostpath-volume-demo
Local : https://github.com/rohankanojia-forks/jkube-testing/tree/main/jkube-local-volume-demo
Host path: https://github.com/rohankanojia-forks/jkube-testing/tree/main/jkube-hostpath-volume-demo
Local : https://github.com/rohankanojia-forks/jkube-testing/tree/main/jkube-local-volume-demo
We do have VolumePermissionEnricher to change mounted directory permission, but it seems to work only when PVC is present.
If you check Local demo, you'll see it's automatically changing permission by adding initContainer
hi all i am trying to run 'hello world' using jkube. the pod generated is giving me imagepullback off. i referred to https://www.tutorialworks.com/kubernetes-imagepullbackoff/ article that says that i might need credentials to access private repositories . Can someone help me out as i am just starting to learn about k8s?@manusa @rohanKanojia
This means the image is not available on Kubernetes Cluster.
If you're running on minikube, you need to run
eval $(minikube -p minikube docker-env) . If you're pushing the image to some external registry, you need to add configuration in your Kubernetes Cluster to add pull secret
is this the right way? @rohanKanojia
Could you please check if there is any open issue https://github.com/eclipse/jkube/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A%22good+first+issue%22 ?
