Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade an existing non-Kubernetes WCS cluster #178

Open
tyskjohan opened this issue Sep 9, 2023 · 1 comment
Open

Upgrade an existing non-Kubernetes WCS cluster #178

tyskjohan opened this issue Sep 9, 2023 · 1 comment

Comments

@tyskjohan
Copy link

tyskjohan commented Sep 9, 2023

How would I use this deployment to upgrade an existing cluster? Basically I would want to skip the RCU creation step and rather point the new cluster at an existing database with an existing repository. Copying the files should be quite straight forward.

@vipinoracle
Copy link

Upgrading non-kubernetes cluster is not possible. I am not sure what product version you are using as of now. Here is what you can do to work around.

  1. If you have customization in sites.war
    A. Create a custom docker image with your customization
    B. Use this image to spin the kubernetes based wcs cluster (No RCU etc is needed)
    C. Make this a target and publish all the sites from non-kubernetes cluster

  2. If there is no customization
    A. Use this default image to spin the kubernetes based wcs cluster (No RCU etc is needed)
    B. Make this a target and publish all the sites from non-kubernetes cluster

Now coming to what you are looking .. like

  1. Pointing to existing db
  2. Pointing to existing file system

Above is possible if file system path in k8s cluster and your existing cluster are same, this would work. Otherwise there would be lot of workaround

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants