
                    For cicd, we pick up the best solutions provided by github life savers.
                    If google brings you here, you are so lucky! These life savers are angels, they have well solved your problems.
                    So do not waste time scrolling the original issue threads just to dig out solutions... 
                    Here you are, you are welcome. Then, go back to work!
                    

I had to fix this earlier today so wanted to share Remediation Steps
1 Describe the bug
On Nov 16th 

argo cd SSH connections to github.com stopped working with host key mismatch

For those getting here through google search it's possible to create a namespace as part of the Application CRD:


Check ArgoCD Application CRD 

argo cd Automatically create namespace with application

The script I have for now is here: https://gist.github.com/ktsakalozos/5de8d4c86c976eeef0242cc39fdf82b2
It would be great if anyone would run it and provide feedback

microk8s root cert expired after a month, cluster does not respond anymore

In v1.14 we restricted the insecure access to MicroK8s from port 8080 to local users only You have two options:


Open insecure port 8080 to everyone 

microk8s Cannot connect to microk8s from another machine

Maybe this will save someone some time In my case the problem was with Azure AD 

argo cd SSO for Existing OIDC Provider returning 401 because of missing client secret

I will have a look at solving this this is a major pain point for us currently too 

argo cd independent version controlled helm values file

Check the version of nginx-ingress controller you're using They made a breaking change starting v0.22.x  

jx Monocular UI does not display charts, it is waiting forever

I forgot to reply to this issue sorry K8s was complaining that the cgroup memory was not enabled Looking at /proc/cgroups was showing memeory disabled 

microk8s Microk8s cluster nodes stuck in NotReady state on ARM64

I was fixed this problem by:

View the old jenkins-docker-cfg secret:



I got the result as follow:


Then base64 encode the <Secret DATA> use echo '<Secret DATA> '' | base64 --decode

jx docker-credential-ecr-login can only be used with Amazon Elastic Container Registry

I just tried microk8s on a server with 1 GB of RAM and it works quite well microk8s.inspect completes in under a minute 

microk8s What are the minimal hardware requirements to run microk8s

The PR with the fix is merged The snap on the edge channel should be available within the next few hours 

microk8s Failed to enable dns

Basically something like this: There are some projects like kubeflow or draft then leverage helm in their solution 

microk8s Add direct support for Helm

Ok here is a workaround that seems to be working (for me at least) Stable Helm Elasticsearch charts https://github.com/helm/charts/tree/master/stable/elasticsearch
fail on Elasticsearch nodes startup:


microk8s.inspect output:


On host:

microk8s Elasticsearch stable Helm charts max file descriptors

I still have this issue on windows Please run microk8s inspect and attach the generated tarball to this issue 

microk8s microk8s (Windows) command not found after fresh installation

Sync-waves have also broken for us after upgrading to 1.8.1 Describe the bug
Using 1.8.1 - app of app sync waves are not working - all the apps sync at once 

argo cd App of apps sync-waves not working in 1.8.1

Hi @Thibaut-ids I spent today figuring out the same information Based on information at https://code-complete.com/code/?p=40 .. 

semaphore How its works ?

After a lot of fiddling So that pipelines invoke sonarqube - either via the SaaS service or a sonarqube chart 

jx Add sonarqube addon

I am also having this issue on fresh Microk8s Deploy a clean microk8s snap deployment:
snap install microk8s --current
Enable DNS 