diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index d31a43110..54e29b583 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -36,7 +36,7 @@ to cover all Airship subprojects. However, airshipctl also has its own specific coding conventions and standards in the official airshipctl [developer guide]( -https://doc.airshipit.org/airshipctl/developers.html). +https://docs.airshipit.org/airshipctl/developers.html). ### Submitting Changes diff --git a/docs/source/phases.rst b/docs/source/phases.rst index 998ef8830..2f14d6d81 100644 --- a/docs/source/phases.rst +++ b/docs/source/phases.rst @@ -183,7 +183,7 @@ Clusterctl executor document example ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - `Executor source - code `__ + code `__ - `Executor API object source code `__ @@ -344,7 +344,7 @@ Cluster map is defined in `Phase bundle <#phase-bundle>`__ as a document. - `Cluster map API object source code `__ - `Cluster map interface source code - `__ + `__ Example of cluster map ~~~~~~~~~~~~~~~~~~~~~~ diff --git a/docs/source/providers/cluster_api_azure.md b/docs/source/providers/cluster_api_azure.md index 1e756062c..63cf30a37 100644 --- a/docs/source/providers/cluster_api_azure.md +++ b/docs/source/providers/cluster_api_azure.md @@ -163,7 +163,7 @@ manifests: commitHash: "" force: false tag: "" - url: https://review.opendev.org/airship/airshipctl + url: https://opendev.org/airship/airshipctl targetPath: /tmp/airship default: phaseRepositoryName: primary diff --git a/docs/source/providers/cluster_api_docker.md b/docs/source/providers/cluster_api_docker.md index e95064e83..0ba1e12a1 100755 --- a/docs/source/providers/cluster_api_docker.md +++ b/docs/source/providers/cluster_api_docker.md @@ -56,7 +56,7 @@ Use target management cluster to deploy workers ### Build [Airshipctl](https://docs.airshipit.org/airshipctl/developers.html) ``` -$ git clone https://review.opendev.org/airship/airshipctl +$ git clone https://opendev.org/airship/airshipctl $ cd airshipctl @@ -97,7 +97,7 @@ manifests: force: false remoteRef: "" tag: "" - url: https://review.opendev.org/airship/airshipctl + url: https://opendev.org/airship/airshipctl metadataPath: manifests/site/docker-test-site/metadata.yaml targetPath: /tmp/airship ``` diff --git a/docs/source/providers/cluster_api_gcp.md b/docs/source/providers/cluster_api_gcp.md index a85e52434..e9987db7a 100755 --- a/docs/source/providers/cluster_api_gcp.md +++ b/docs/source/providers/cluster_api_gcp.md @@ -202,7 +202,7 @@ manifests: force: false remoteRef: "" tag: "" - url: https://review.opendev.org/airship/airshipctl + url: https://opendev.org/airship/airshipctl metadataPath: manifests/site/gcp-test-site/metadata.yaml targetPath: /tmp/airship ``` diff --git a/docs/source/providers/cluster_api_openstack.md b/docs/source/providers/cluster_api_openstack.md index e7eab4319..0f52d66b7 100755 --- a/docs/source/providers/cluster_api_openstack.md +++ b/docs/source/providers/cluster_api_openstack.md @@ -154,7 +154,7 @@ cd image-builder/images/capi/ vim packer/qemu/qemu-ubuntu-1804.json ``` -Update the iso_url to `http://cdimage.ubuntu.com/releases/18.04/release/ubuntu-18.04.5-server-amd64.iso` +Update the iso_url to `http://cdimage.ubuntu.com/releases/18.04/release/ubuntu-18.04.6-server-amd64.iso` Make sure to use the correct checksum value from [ubuntu-releases](http://cdimage.ubuntu.com/releases/18.04.5/release/SHA256SUMS) diff --git a/docs/source/secrets-guidelines.md b/docs/source/secrets-guidelines.md index bc87a002c..8a1f0a15a 100644 --- a/docs/source/secrets-guidelines.md +++ b/docs/source/secrets-guidelines.md @@ -35,7 +35,7 @@ secretGroups: pinned: true|false #optional ``` -This structure allows to split data into groups each of them can be regenerated/updated separatelly. For that purpose it has `updated` field timestamp that is getting new value when regeneration of group is happening. Each group has an array of values. Each value has a name (should be unique in the group), data field and also optional flag `pinned`. If the value is pinned, its value isn't getting updated during regeneration. That may be helpful to flexibly switch between 'internally generated' and 'externally provided' secrets. `pinned: true` will work as 'exnternally provided'. +This structure allows to split data into groups each of them can be regenerated/updated separately. For that purpose it has `updated` field timestamp that is getting new value when regeneration of group is happening. Each group has an array of values. Each value has a name (should be unique in the group), data field and also optional flag `pinned`. If the value is pinned, its value isn't getting updated during regeneration. That may be helpful to flexibly switch between 'internally generated' and 'externally provided' secrets. `pinned: true` will work as 'externally provided'. Airshipctl will encrypt only field `data` and that will allow to monitor all other parameters without knowing master keys for decryption. @@ -57,7 +57,7 @@ Airshipctl uses kustomize along with different krm-functions that extend its fun * Templater krm-function that is needed to produce new yaml documents based on the provided parameters. There is a standard catalog of [krm-functions](https://github.com/GoogleContainerTools/kpt-functions-catalog). -It includes the standard krm-function: `gcr.io/kpt-fn-contrib/sops` that can be used to perform decryption and encryption right in kustomize. Please refer to the [example configurations](https://github.com/GoogleContainerTools/kpt-functions-catalog/tree/master/examples/contrib/sops) that can be used to encrypt and decrypt the set of existing yamls. +It includes the standard krm-function: `gcr.io/kpt-fn-contrib/sops` that can be used to perform decryption and encryption right in kustomize. Please refer to the [example configurations](https://github.com/GoogleContainerTools/kpt-functions-catalog/tree/master/contrib/examples/sops-age) that can be used to encrypt and decrypt the set of existing yamls. Please note that to make that krm-function work it’s necessary to provide the following ENV variables: diff --git a/docs/source/virtual_redfish_bmc.md b/docs/source/virtual_redfish_bmc.md index 71fb633d6..f32fd16d8 100644 --- a/docs/source/virtual_redfish_bmc.md +++ b/docs/source/virtual_redfish_bmc.md @@ -131,6 +131,7 @@ For experimental/smaller setups the following method can also be used. ##### Download the Redfish_tools.zip archive and build the redfish emulator VM [Redfish_tools.zip](https://github.com/dell-esg/tool-pkgs/blob/master/Redfish_tools.zip) +Note: tools-pkgs repository have been deprecated from dell-esg so this link leads to 404 ##### Scp the redfish_tools zip to the host machine diff --git a/manifests/function/cni/tigera-operator/README.rst b/manifests/function/cni/tigera-operator/README.rst index 5586cc27f..6b9b49286 100644 --- a/manifests/function/cni/tigera-operator/README.rst +++ b/manifests/function/cni/tigera-operator/README.rst @@ -11,7 +11,7 @@ This function contains a Kubernetes operator which manages the lifecycle of a Ca To know more about tigera installation see the `installation reference`_. -.. _tigera-operator.yaml: https://github.com/airshipit/airshipctl/tree/master/manifests/function/tigera-operator/v1.15.0/upstream/tigera-operator.yaml -.. _custom-resources.yaml: https://github.com/airshipit/airshipctl/tree/master/manifests/function/tigera-operator/v1.15.0/custom-resources.yaml +.. _tigera-operator.yaml: https://github.com/airshipit/airshipctl/tree/master/manifests/function/cni/tigera-operator/v1.15.0/upstream/tigera-operator.yaml +.. _custom-resources.yaml: https://github.com/airshipit/airshipctl/tree/master/manifests/function/cni/tigera-operator/v1.15.0/custom-resources.yaml .. _GitHub URL: https://docs.projectcalico.org/manifests/tigera-operator.yaml .. _installation reference: https://docs.projectcalico.org/getting-started/kubernetes/quickstart