Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Rafael de Andrade Sousa
    @rafaelsousa
    image.png
    (image is very small, :D)
    Marc Nuri
    @manusa

    Passed through command line?

    Maven properties:

    <properties>
      <jkube.enricher.jkube-controller.pullPolicy>Never</jkube.enricher.jkube-controller.pullPolicy>
    </properties>

    Or command line: mvn ... -Djkube.enricher.jkube-controller.pullPolicy=Never

    Rafael de Andrade Sousa
    @rafaelsousa
    Alright :) thank you
    Marc Nuri
    @manusa
    Regarding your problem, the default (IfNotPresent) should work as expected
    Are you sure that your cluster's registry has that image available?
    Rafael de Andrade Sousa
    @rafaelsousa
    the cluster registry is different from the docker registry?
    Marc Nuri
    @manusa
    Well, the cluster has an internal docker registry
    So if you are building your image in your machine, the docker registry in your machine is not the same as the one in the cluster
    if you are using Minikube you can use the remote/cluster Docker daemon by invoking $ eval $(minikube docker-env)
    Rafael de Andrade Sousa
    @rafaelsousa
    ❌ Exiting due to ENV_MULTINODE_CONFLICT: The docker-env command is incompatible with multi-node clusters. Use the 'registry' add-on: https://minikube.sigs.k8s.io/docs/handbook/registry/
    rsousa@tardis:~/Software$
    I think we find the problem, right?
    I am enabling the addon to see if this works
    Marc Nuri
    @manusa
    oh, TIL
    Rafael de Andrade Sousa
    @rafaelsousa
    What does it stand for?
    Marc Nuri
    @manusa
    sorry, Today I learned
    Rafael de Andrade Sousa
    @rafaelsousa
    I REALLY learned today. Here, ☕, have a coffee on me
    Marc Nuri
    @manusa
    :) thx
    Out of curiosity, what's the main reason for you to run Minikube as multinode?
    Rafael de Andrade Sousa
    @rafaelsousa
    None... This feature is experimental and I am always running in the wild hahaha
    And, maybe if something breaks, I could report to a possible bug report.
    Marc Nuri
    @manusa
    Good. Please, let us know if the registry addon fixes the problem.
    Rafael de Andrade Sousa
    @rafaelsousa
    Hi, it worked, by I had to restart minikube with only one node.
    Have other problems now, but is application related. Thank you so much @manusa !
    Marc Nuri
    @manusa
    No problem, thanks for trying out JKube ;)
    Rafael de Andrade Sousa
    @rafaelsousa
    It's my honour!
    As a dev java, I'd like to collaborate one day if the occasion presents itself
    Marc Nuri
    @manusa
    PRs are welcome. Please let us know to if you need any assistance creating a PR. We'll also try to find time to create a few more "first-time"/"help-wanted" issues.
    Rohan Kumar
    @rohanKanojia
    Hi guys, @manusa would be giving us a brief overview about Eclipse JKube in EclipseCon 2020 tomorrow. Please join us in case you're interested in this project as a user/want to get involved. Here is a link to the talk: https://www.eclipsecon.org/2020/sessions/deploy-your-java-applications-cloud-using-eclipse-jkube?utm_content=142365277&utm_medium=social&utm_source=twitter&hss_channel=tw-1177549444935487488
    Rohan Kumar
    @rohanKanojia
    In case anyone didn't get chance to attend, here is a recording to JKube's talk at EclipseCon: https://www.youtube.com/watch?v=vgIwRX4LXfU
    Marc Nuri
    @manusa
    Starting release process for 1.0.2
    Rohan Kumar
    @rohanKanojia
    :+1:
    Rohan Kumar
    @rohanKanojia
    cool, Thanks for the release.
    Georg Schmidt-Dumont
    @georgschmidtdumont

    Hi, I am trying to deploy my spring boot app to openshift using the jkube openshift maven plugin. I'm using yml files for the config. Whatever I do, I run into the following exception:
    Execution omp of goal org.eclipse.jkube:openshift-maven-plugin:1.0.2:resource failed: No resource type found for:v1#Deployment

    I have a deployment.yml residing in src/main/jkube and it is successfully copied to target/jkube/deployment.yml

    The content of the deployment.yml are

    apiVersion: v1
    kind: Deployment
    metadata:
      name: ${project.artifactId}
    spec:
      template:
        spec:
          containers:
            - env:
                - name: SSL_KEY_PASSWORD
                  valueFrom:
                    secretKeyRef:
                      name: ssl-secrets
                      key: key-password
                - name: KEYSTORE_PASSWORD
                  valueFrom:
                    secretKeyRef:
                      name: ssl-secrets
                      key: keystore-password
                - name: TRUSTSTORE_PASSWORD
                  valueFrom:
                    secretKeyRef:
                      name: ssl-secrets
                      key: truststore-password
                - name: JAVA_OPTIONS
                  value: "-Dspring.profiles.active=openshift"

    any input on what the issue might be is highly appreciated!

    Marc Nuri
    @manusa
    Please, try to remove the apiVersion field
    Rohan Kumar
    @rohanKanojia
    @georgschmidtdumont :Deployment's apiVersion is apps/v1 not v1
    Georg Schmidt-Dumont
    @georgschmidtdumont
    Thanks @rohanKanojia and @manusa !
    Rohan Kumar
    @rohanKanojia
    np, Thanks for trying out Eclipse JKube!
    Marc Nuri
    @manusa
    Sprint 192 Review recording is now available https://www.youtube.com/watch?v=I3pjd0D90gA
    Rohan Kumar
    @rohanKanojia
    :+1:
    Georg Schmidt-Dumont
    @georgschmidtdumont
    Hi, I have setup an OpenShift deployment for a Spring Boot App and have run into the Problem that the user in the base image I am using is either not numeric or not in the allowed range
    error: build error: image "my-base-image" must specify a user that is numeric and within the range of allowed users
    Since I cannot change the base image I thought I change the jkube config in order to build the image using the local Docker daemon. As I understand I need to set the jkube.docker.host property. Unfortunately this does not seem to work as JKube is still running in OpenShift mode. What am I missing to get jkube to run in Kubernetes mode?
    Marc Nuri
    @manusa
    Use kubernetes-maven-plugin to build your image, then openshift-maven-plugin to generate your resources
    However, the problem is with your base image, you should make sure that your image doesn't require a special USER to run. This won't work on OpenShift.
    Does your base image do anything special? would you consider to use JKube's standard base image?