On my daily work I have to switch context while in the middle of a modification many times,
or I just have to work on two different versions in parallel.
Working with git
there are many ways to save your work and come back later,
but I have found all of them too cumbersome in the process to resume work.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
apiVersion: machine.openshift.io/v1beta1 | |
kind: MachineSet | |
metadata: | |
labels: | |
machine.openshift.io/cluster-api-cluster: aravindh-winc-6h9df | |
name: aravindh-winc-6h9df-windows-worker-a | |
namespace: openshift-machine-api | |
spec: | |
replicas: 1 | |
selector: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
## OpenShift4 pull-secret: | |
1. Download your pull-secret from [console.redhat.com](https://console.redhat.com/openshift/install/aws/installer-provisioned) | |
- click on “Download Pull Secret”. Save it somewhere, e.g. ~/some-dir/pull-secret | |
2. Add the apps.ci auth to pull-secret! _internal OpenShift developers only_ | |
- Obtain an API token by visiting https://oauth-openshift.apps.ci.l2s4.p1.openshiftapps.com/oauth/token/request | |
copy the oc login cmd and paste in terminal to login to the ci cluster, then run this: | |
- `$ oc registry login --to ~/some-dir/pull-secret` | |
This will append the auth from registry.ci.openshift.org to your cloud.openshift.com pull-secret but it will also | |
make the pull-secret multi-line. |