meanwhile I get the feeling, that the setup process is not finished after the welcome screen appears.
As I did not check the result directly after the installation has been finished in the first one or two days, I maybe did not realize, that there are still ongoing steps and processes with some delays.
Playing around with the environment a bit more today, I did a kubectl output more than two hours ago and compared it with a fresh one. I´ll add them as a pdf, as there is no chance to add them as text.
Also, I´m not allowed to add more than three posts in a row w/o any answer in between…strange…
kubectl_outputs.pdf (124.3 KB)
As you can see, the second output shows some of the missing services. Now, the first service IPs are coming, e.g. argocd-staging-nginx or pet-clinic.
Meanwhile, these IP addresses are usable inside the browser and the corresponding pipelines are appearing automatically in Jenkins.
I did nothing, just let the system run.
But what does this mean? I added 6 virtual CPUs and 6GB memory to my both test systems.
How many resources are needed for this playground? Unfortunately, I did not really find an answer for this.
Another question, several of the status and service information are in “pending” state.
Checking top, I see that the swap space is nearly out, but no load - well not at the moment or last minutes:
But at the end I see now the same behavior in ArgoCD as before in the last days - what brings me to the next question: after starting the playground, all fields are green and in sync inside ArgoCD.
But understanding now, that at this time not everything is up as expected maybe, that overview seems not to show the truth right now, or am I wrong?
Now, in that kubectl output state with all these pendings, I see that information inside ArgoCD view:
Coming back to the kubectl output - aside the services in staging state, I would also expect services with or for production stage, right? Otherwise, it would not make sense for me, why some of the IPs are available as described in your manual and some are not so far (all production ones are missing atm).
How to move forward? Do I have to wait one or two further days that everything is active, up and running? How can I check that the “normal” playground situation is reached and I can start playing with it?
Do I have to add more CPU´s or memory? What about the swap area, is that one maybe also too small? I saw warning talking about low swap area inside Jenkins.
What about moving to another k3s environment instead of using one K3d system which has to handle everything inside with docker?
May I ask for some information regarding the specifications for a k3s environment?
Just let me know if you need any log file or further information.
Many thanks and best regards,