Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Marc Nuri
    @manusa
    Have you checked the logs in the pod used to perform the build?
    it should be named something like spring-boot-s2i-1-build
    Maybe the log is clearer there
    but it really seems a problem with your cluster
    Marc Nuri
    @manusa
    Hello everyone!
    Today we'll be hosting Eclipse's J4K virtual booth from 11 am to 1pm (EDT)
    https://www.crowdcast.io/e/j4kbooth_eclipse/4
    Please join us for the latest news about the project and to get live responses to any questions you may have
    Rohan Kumar
    @rohanKanojia
    Thanks for sharing! Looking forward to joining it :-)
    Rafael de Andrade Sousa
    @rafaelsousa
    Hi @all, I have the following maven config :
    <configuration>
                        <namespace>cassandra</namespace>
                        <imagePullPolicy>never</imagePullPolicy>
                        <images>
                            <image>
                                <name>pm/service-task</name>
                                <alias>service-task</alias>
                                <build>
                                    <from>openjdk:11</from>
                                    <assembly>
    ...
    </configuration>
    However, when running mvn k8s:build k8s:resource
    spec:
          containers:
          - env:
            - name: KUBERNETES_NAMESPACE
              valueFrom:
                fieldRef:
                  fieldPath: metadata.namespace
            - name: HOSTNAME
              valueFrom:
                fieldRef:
                  fieldPath: metadata.name
            image: pm/service-task:latest
            imagePullPolicy: IfNotPresent
    The imagePullPolicy remains IfNotPresent.
    What am I doing wroing here?
    Thank you!
    You want to configure the pull policy for the enricher (not image)
    The XML configuration element is <pullPolicy>
    You can either use the property jkube.enricher.jkube-controller.pullPolicy
    Or:
    <configuration>
      <enricher>
        <config>
          <jkube-controller>
            <pullPolicy>Never</pullPolicy>
          </jkube-controller>
        </config>
      </enricher
    </configuration>
    Rafael de Andrade Sousa
    @rafaelsousa

    You can either use the property jkube.enricher.jkube-controller.pullPolicy

    Passed through command line?

    Thanks, it worked! However the outcome I was expecting didn't happen.
    I wanted the kubernetes deployment do not pull the image from a remote registry, since the image is already local
    Rafael de Andrade Sousa
    @rafaelsousa
    rsousa@tardis:~/Code/personalmanager/service-plannedtask$ docker image ls
    REPOSITORY                            TAG                   IMAGE ID            CREATED             SIZE
    pm/service-task                       latest                bed1bd90616c        2 minutes ago       675MB
    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