Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 19:56
    andreaTP commented #4313
  • 19:56
    andreaTP commented #4313
  • 19:41
    andreaTP commented #4313
  • 18:00
    renannprado commented #4313
  • 17:52
    andreaTP commented #4313
  • 15:50
    renannprado starred fabric8io/kubernetes-client
  • 14:22
    manusa edited #4328
  • 14:20
    manusa closed #4315
  • 14:20

    manusa on master

    Generate enum values when index… Add generated sources to be rec… Refactor enums to parse indexes… (compare)

  • 14:20
    manusa closed #4328
  • 14:20
    manusa milestoned #4328
  • 13:55
    sonarcloud[bot] commented #77
  • 13:55
    sonarcloud[bot] commented #77
  • 13:48
    sonarcloud[bot] commented #83
  • 13:48
    sonarcloud[bot] commented #83
  • 13:25
    manusa edited #4322
  • 13:18
    shawkins commented #4318
  • 13:18
    shawkins closed #4318
  • 12:21
    sonarcloud[bot] commented #154
  • 10:37
    yuntianfeijing starred fabric8io/kubernetes-client
Rohan Kumar
@rohanKanojia
Do you have some simple reproducer project which we can try out?
I havent really used fabric8 with Eclipse.. I usually build a maven project and load as a maven project in IntelliJ
emrealpogunc
@emrealpogunc
Will give intellij a shot ^_^ Thank you so much for the recommendation.
Rohan Kumar
@rohanKanojia
I think it might also be possible to build maven project and load in Eclipse as maven project
emrealpogunc
@emrealpogunc
I tried intellij and did just like you've said(build and load as a maven project) and right now everything seems fine. I think I've found some of your tutorials and articles on the web and I'm trying to learn through them atm. Thank you once again👍
Rohan Kumar
@rohanKanojia
my tutorials?
emrealpogunc
@emrealpogunc
https://developers.redhat.com/blog/2020/05/20/getting-started-with-the-fabric8-kubernetes-java-client# by tutorials I meant this article in particular, I might have misused the term "tutorial" a bit, apologies If I caused an inconvenience.
Rohan Kumar
@rohanKanojia
oh, I see.
No need to apologize.
emrealpogunc
@emrealpogunc
I get exited when I'm talking with you talented people so I might apologize or thank for unnecessary reasons (I know it's silly but I can't help myself :D)
Rohan Kumar
@rohanKanojia
:-) ohk, I see. It's normal for everyone who is new to some group.
emrealpogunc
@emrealpogunc
It's good to know that I'm not alone with such behavior :D also I have a question, while I don't have any tasks atm(I'm an intern) , I want to study fabric8, What do you think is the most important part of using fabric8 (Java sdk specifically) ? What skill is a necessity for your job? Im fairly new to the professional side of software engineering so I was wondering these topics ^_^
Rohan Kumar
@rohanKanojia
If you're working around Kubernetes and Java. I'll suggest reading about basic kubernetes concepts from Kubernetes documentation
We also have a cheatsheet for managing different kubernetes resources from fabric8 https://github.com/fabric8io/kubernetes-client/blob/master/doc/CHEATSHEET.md
I think writing Kubernetes Operators can be also something interesting to learn
there is Java Operator SDK as well which uses fabric8 internally : https://github.com/java-operator-sdk/java-operator-sdk
emrealpogunc
@emrealpogunc
Thank you so much Im going to study all of them, once again I'm really appreciated 😁👍👍👍
Sachin Mittal
@sjmittal
Folks I had a doubts regarding waitUntilReady on a pod resource
when does it actually returns a pod, when all the containers are in running state or if any one container is in ready state ?
5 replies
is there any api which actually checks if a particular container is ready or not ?
2 replies
Mohd Uzair
@MUzairS15
@sjmittal When all the containers are in running state, pod gets ready.
Kubelet does thr readiness check and tells if pod is running and accessible or not
Pls correct me if I am wrong.
emrealpogunc
@emrealpogunc
Hi everyone, I'm having an issue and wanted to know the reason behind it. I created a github issue so it's easier to read and fathom the problem. Thank you all so much fabric8io/kubernetes-client#3356
Rohan Kumar
@rohanKanojia
hello
Did you create a custom resource after running operator
kubectl apply -f src/main/resources/cr.yaml
I had also created a video regarding this https://www.youtube.com/watch?v=uxR7Mfpn9HI . If you go to the end of the video. You might see it in action(audio is not great quality but you might be able to get some idea)
emrealpogunc
@emrealpogunc
Thanks to your answer sir, I fixed the issue! I also replied to your answer via GitHub as well. Thank you so much!
Jakub Cechacek
@jcechace

@rohanKanojia Hi... here with the same project again. https://github.com/jcechace/apicurio-model-generator

It's becoming gradually more important for us to generate this model for current revisions of apicurio. THe issue is that my understanding of that project (and gomodules in general) is on the low side. Would you be willing to schedule a call with me and go over the project? For example I'd very much like to understand the versioning as changing the version of github.com/fabric8io/kubernetes-client/generator to comment matching the v5.6.0 release tag breakes the project and so on.

Rohan Kumar
@rohanKanojia
Hi, I'll look into this. I'll check if the model can be easily updated to 5.6.0. Maybe a call might not be required at all
Jakub Cechacek
@jcechace
@rohanKanojia v1.0.0 is the right branch if you want to have a look .
Rohan Kumar
@rohanKanojia
cool, I'll try looking into this after work
Jakub Cechacek
@jcechace
@rohanKanojia probably the most desirable thing is to generate POJOs which would extend CustomResource so I don't have to load yaml CRDs in my code (as that's deprecated and requires me to actually get hold of those descriptors).
thank you
Rohan Kumar
@rohanKanojia
I realized the reason why we had to add a hack for replacing javaType with existingJavaType was due to a hardcoded check added in generator during JSONSchema2Pojo upgrade
I have created an issue for this fabric8io/kubernetes-client#3372
so if I remove the hack and use latest generator, it works if I rename package to io.fabric8.apicurio.registry.operator.api.model. rohanKanojia/apicurio-model-generator@8b6ad96
I'll probably create a PR to your repository once above issue gets fixed
Rohan Kumar
@rohanKanojia

probably the most desirable thing is to generate POJOs which would extend CustomResource so I don't have to load yaml CRDs in my code (as that's deprecated and requires me to actually get hold of those descriptors).

I think we can do it by providing a manual ApicurioRegistry and ApicurioRegistryList which will extend CustomResource

we can add a delete task to maven-antrun-plugin to delete generated ApicurioRegistry class and use hand written class which will extend CustomResource
Jakub Cechacek
@jcechace

probably the most desirable thing is to generate POJOs which would extend CustomResource so I don't have to load yaml CRDs in my code (as that's deprecated and requires me to actually get hold of those descriptors).

I think we can do it by providing a manual ApicurioRegistry and ApicurioRegistryList which will extend CustomResource

Loading the yaml descriptor seems cleaner in that case. Writing the classes doesn't really seem as a good option and thus I think this method shouldn't be deprecated -- the majority of CR/Ds one is going to encounter are not going to be written in java.

Rohan Kumar
@rohanKanojia
I think you're right
I also think this method should not be deprecated. It will come handy when you're trying to use same pojo for different customresource versions fabric8io/kubernetes-client#2738
I think we should create a new issue to start this discussion again
Rohan Kumar
@rohanKanojia

the majority of CR/Ds one is going to encounter are not going to be written in java.

I think I see more and more people interested in writing operators in java these days

Red Hat is also investing some resources in java operator sdk
Jakub Cechacek
@jcechace
Yes but we should strive for general usability :)

@rohanKanojia
btw did you ever see this? Without touching my cluster the client starting spitting this at me

Caused by: io.fabric8.kubernetes.client.WatcherException: too old resource version: 48308901 (48321468)

5.2.1 client

Jakub Cechacek
@jcechace
Ok I supsect some micro release update in the cluster broke something. Updating to 5.5 fixed it