Skip to content

Commit 6715ff2

Browse files
committed
remove The OCM : Image in Docs
Signed-off-by: adity1raut <araut7798@gmail.com>
1 parent dc9ec5f commit 6715ff2

File tree

1 file changed

+0
-75
lines changed

1 file changed

+0
-75
lines changed

docs/contributors.md

Lines changed: 0 additions & 75 deletions
Original file line numberDiff line numberDiff line change
@@ -91,78 +91,3 @@ LATEST_TAG=<tag used for image> make ko-build-push-cmupdate
9191

9292
1. To avoid leaving a time bomb, delete that `brew` branch after it was merged into `main` (the goreleaser will fail to create the new `brew` branch if one already exists).
9393

94-
95-
## OCM Images
96-
97-
### Commands to build & publish multicluster-controlplane from fork
98-
99-
At this time the official multicluster-controlplane has issues and a build from
100-
a fork is required. We expect to re-evaluate when new images will be published
101-
by the OCM community.
102-
103-
1. Build and publish image from fork
104-
105-
```shell
106-
git clone https://github.com/pdettori/multicluster-controlplane.git
107-
cd multicluster-controlplane
108-
git checkout kubeflex
109-
make image
110-
docker tag quay.io/open-cluster-management/multicluster-controlplane:latest quay.io/kubestellar/multicluster-controlplane:v0.2.0-kf-alpha.1
111-
docker push quay.io/kubestellar/multicluster-controlplane:v0.2.0-kf-alpha.1
112-
```
113-
### Commands to package and push a chart to a OCI registry
114-
115-
First clone and build image as explained in [Commands to build & publish multicluster-controlplane from fork](#commands-to-build--publish-multicluster-controlplane-from-fork), then:
116-
117-
```shell
118-
helm package charts/multicluster-controlplane --version v0.2.0-kf-alpha.1
119-
helm push *.tgz oci://quay.io/kubestellar
120-
```
121-
122-
### Hosting a copy of postgresql chart and image on quay.io
123-
124-
1. Select the desired postgresql chart tag:
125-
126-
For example `CHART_TAG=13.1.5`.
127-
128-
2. Pull the chart from the bitmani Docker registry:
129-
130-
```shell
131-
helm pull oci://registry-1.docker.io/bitnamicharts/postgresql:$CHART_TAG
132-
```
133-
134-
3. Unpack the downloaded `postgresql-$CHART_TAG.tgz` archive:
135-
136-
```shell
137-
tar xf postgresql-$CHART_TAG.tgz
138-
```
139-
140-
4. In the newly created `postgresql` folder open the `values.yaml` and find the `image:` section:
141-
142-
- Change the `registry:` from `docker.io` to `quay.io`.
143-
- Change the `repository:` from `bitnami/postgresql` to `kubestellar/postgresql`.
144-
- Take note of the image tag, for example `IMAGE_TAG=16.0.0-debian-11-r13`.
145-
146-
5. Repackage the chart in a tarball with the same name:
147-
148-
```shell
149-
tar czf postgresql-$CHART_TAG.tgz postgresql/
150-
```
151-
152-
6. Push the customized chart to quay.io:
153-
154-
```shell
155-
helm login quay.io
156-
helm push postgresql-$CHART_TAG.tgz oci://quay.io/kubestellar/charts
157-
```
158-
159-
7. Update the postgresql Helm chart reference that is hard coded in [postgresql.yaml](../chart/templates/postgresql.yaml#L97) to match the quay.io registry, repository, and tag used in the Helm push command of step 6.
160-
161-
8. Make a multi-arch copy of postgresql container image from `docker.io` to `quay.io` to match the customized chart image reference:
162-
163-
```shell
164-
docker login quay.io
165-
docker buildx imagetools create --tag quay.io/kubestellar/postgresql:$IMAGE_TAG docker.io/bitnami/postgresql:$IMAGE_TAG
166-
```
167-
168-
The registry, repository, and tag used in this command must match the values included in the customized chart at step 4.

0 commit comments

Comments
 (0)