openshift-migration-best-practices - GitLite

KO | EN

gitlite — search

#python #hacktoberfest #ai #golang #rust #linux #nodejs #java #windows #awesome #kubernetes #vue #security #mcp

openshift-migration-best-practices

(★ 72)

Best practices for migrating from OpenShift 3 to 4

파일 탐색기

최종 버전 다운로드 (.zip)

- - broken-link-check.yml
  - greetings.yml
  - jekyll.yml
  - label.yml
  - stale.yml
- dependabot.yml
- labels.yml
- - breadcrumbs.liquid
  - content.liquid
- dvm-display-failure-list.template
- migmigration-completed-list.template
- migmigration-display-warning-list.template
- ci-cd-promotion-flow.png
- CRDArch.png
- DebugTree.png
- home.png
- migration-strategy-audience.png
- migration-strategy-bigbang.png
- migration-strategy-canary.png
- migration-strategy-individual.png
- mtc-1.4.z-debugging-guide.jpeg
- mtc-architecture.png
- mtc-promotion-flow.png
- openshif4-operatorhub.png
- operator-maturity-levels.png
- ResourceDebugKebabOption.png
.gitignore
.pre-commit-config.yaml
.yaspeller.json
01-planning.md
02-cluster-health-checks.md
03-pre-migration-testing.md
04-running-the-migration.md
05-troubleshooting.md
06-post-migration-considerations.md
_config.yml
Gemfile
index.md
README.md

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Best practices for migrating from OpenShift&nbsp;Container&nbsp;Platform&nbsp;3&nbsp;to&nbsp;4

Check <https://redhat-cop.github.io/openshift-migration-best-practices/> for the rendered version of the documents.

## Contributing

Read the [Guidelines for Red Hat Documentation](https://redhat-documentation.github.io/) before opening a pull request.

You can test the changes to this repository via a container.

### Run a Jekyll container

- Clone repository, check out source branch and prepare the Jekyll site

```console
  git clone -b source https://github.com/redhat-cop/openshift-migration-best-practices.git && cd openshift-migration-best-practices
  for i in .jekyll-cache _site; do mkdir ${i} && chmod 777 ${i}; done
  for i in Gemfile.lock; do touch ${i} && chmod 777 ${i}; done
  ```

- On a SELinux enabled OS:

```console
  podman run -it --rm --name jekyll -p 4000:4000 -v $(pwd):/srv/jekyll:Z jekyll/jekyll jekyll serve --watch --future
  ```

**NOTE**: The Z at the end of the volume (-v) will relabel its contents so that it can be written from within the container, like running `chcon -Rt svirt_sandbox_file_t -l s0:c1,c2` yourself. Be sure that you have changed your present working directory to the git cloned directory as shown above.

- On an OS without SELinux:

```console
  podman run -it --rm --name jekyll -p 4000:4000 -v $(pwd):/srv/jekyll jekyll/jekyll jekyll serve --watch --future
  ```

### View the site

Visit `http://<localhost>:4000` in your local browser.