mirror of
https://github.com/hyperledger/fabric-samples.git
synced 2026-06-19 00:15:08 +00:00
a299e18e26
* Import Full Stack Asset Transfer Guide at commit fb554befdbbeff9e69159b54fce0b811603f29c7 Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com> * Update the workshop with a new WORKSHOP_PATH under fabric-samples Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com> * Update the workshop with a new WORKSHOP_PATH under fabric-samples Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com> * missed a .git ignored directory on add Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com> * Updates to run the workshop on the Apple M1 Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com> * Workaround for https://github.com/eslint/eslint/issues/15299 in the contract tslinter Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com> * Build an arch-specific CC images on M1 Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com> * empty commit - force a build Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com> * revert an accidental commit that was building the top-level asset-transfer as arm64 Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com> Signed-off-by: Josh Kneubuhl <jkneubuh@us.ibm.com>
41 lines
No EOL
1.4 KiB
Markdown
41 lines
No EOL
1.4 KiB
Markdown
# Notes on deployment with OpenShift
|
|
|
|
There are minor variations in deploying to each different K8S environment; these notes are for open shift specifically
|
|
|
|
## Login
|
|
|
|
Typically for setup the local k8s context you should login to OpenShift onthe command line; this usually uses token based authentication rather than a password.
|
|
|
|
## Storage Classes
|
|
|
|
If you don't have any storage classes created by default...
|
|
|
|
```
|
|
CLUSTER_TYPE=ocp ./infrastructure/setup_storage_classes.sh
|
|
```
|
|
|
|
This uses rook to create storage classes
|
|
Set the setup_storage_classes
|
|
|
|
```
|
|
WORKSHOP_STORAGE_CLASS=rook-cephfs
|
|
```
|
|
|
|
## Image Registry
|
|
|
|
Using the built in image registry is possible.
|
|
|
|
Follow the instructions at https://docs.openshift.com/container-platform/4.8/registry/accessing-the-registry.html to create a user and permissions that allow for pushing and pulling from the registry
|
|
|
|
Expose the registry externally with instructions at https://docs.openshift.com/container-platform/4.8/registry/securing-exposing-registry.html
|
|
|
|
## Image names
|
|
|
|
Note the name used externally is different from the internal name of the image. The name in the chaincode package MUST be the internal name
|
|
|
|
As an example for a bare-metal OpenShift cluster these where the internal and external names of the same image
|
|
|
|
```
|
|
WORKSHOP_EXTERNAL_REPO=default-route-openshift-image-registry.apps.report.cp.fyre.ibm.com:443
|
|
WORKSHOP_INTERNAL_REPO=image-registry.openshift-image-registry.svc:5000
|
|
``` |