leduy123lsdd commented on issue #4938: URL: https://github.com/apache/skywalking/issues/4938#issuecomment-1610911122
> > My steps to fix this issue if you using Helm to install skywalking > > > > 1. Get skywalking-oap-init Job template > > > > > > * execute: `helm template skywalking oci://registry-1.docker.io/apache/skywalking-helm -n skywalking > manifest.yaml` > > > > > > 2. Extract Job from manifest.yaml > > > > > > * in manifest.yaml, search for "kind: Job" and copy entire Job manifest to new file called: init-oap.yaml > > > > <img alt="Screenshot 2023-06-28 at 09 10 00" width="1020" src="https://user-images.githubusercontent.com/37374066/249326070-4af8cd63-a439-4601-a3d4-09a208c94aca.png";> > > > > * Delete old job if it existed: `kubectl delete -f init-oap.yaml -n skywalking` > > * Execute the job: `kubectl create -f init-oap.yaml -n skywalking` > > > > > > 3. Lastly, restart oap service pods. And voila, sky walking is back. > > > > This solution is just temporary fix and it will happen next time when k8s got restarted > > No need to do so now. The init job will be executed on installation and upgrade now the problem is when k8s restart it running into OAP is running in 'no-init' mode. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
![https://user-images.githubusercontent.com/37374066/249326070-4af8cd63-a439-4601-a3d4-09a208c94aca.png"](https://user-images.githubusercontent.com/37374066/249326070-4af8cd63-a439-4601-a3d4-09a208c94aca.png"){kind=link}