Skip to content

Commit 0fbfdd2

Browse files
authored
Remove HyperShift edge install (#44)
* Remove HyperShift edge install * un-used * more * update readme * always install gitops
1 parent 340de1b commit 0fbfdd2

26 files changed

+174
-653
lines changed

README.md

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,7 @@
11
## Overview
22
The purpose of this project is to ease the setup of a provisioning cluster, as well as ease the process of installing an edge cluster.
33

4-
Standard Install:
5-
* After the installation of an edge cluster is complete, the edge cluster does not depend on the provisioning cluster for anything. The provisioning cluster is simply an installer.
6-
7-
HyperShift Install:
8-
* The provisioning cluster hosts the control plane for the edge cluster. The edge cluster has no control plane nodes.
4+
After the installation of an edge cluster is complete, the edge cluster does not depend on the provisioning cluster for anything. The provisioning cluster is simply an installer.
95
## Prerequisites
106
* Provisioning Cluster:
117
* Pre-existing OpenShift cluster (SNO, compact, or standard).

SALES_PITCH.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,6 @@
88
* Option to auto approve CSRs (for edge clusters that may be offline for extended periods).
99
* Re-uses install-config.yaml (IPI install config) for configuration.
1010
* Easy to read Ansible playbook, what you see is what you get.
11-
* Can deploy HyperShift (Hosted Control Plane) clusters.
1211

1312
## How do I do GitOps?
1413
The edge cluster install config files can be committed to a Git repo. You could then configure a CI/CD pipeline (GitHub Actions, Gitlab CI, etc) to execute the Ansible playbook using those files as inputs whenever a change is committed to the repo.

edge/README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
# Purpose
2-
This playbook installs an edge cluster. You should already have a provisioning cluster configured. See [HYPERSHIFT.md](docs/HYPERSHIFT.md) for information on setting up a cluster using Hosted Control Planes.
2+
This playbook installs an edge cluster. You should already have a provisioning cluster configured.
33
# Usage
4-
Example [install config](https://docs.openshift.com/container-platform/latest/installing/installing_bare_metal_ipi/ipi-install-installation-workflow.html#additional-resources_config) files are provided in ```install-config-sno-example.yaml```, ```install-config-standard-example.yaml``` and ```install-config-hypershift-example.yaml```.
4+
Example [install config](https://docs.openshift.com/container-platform/latest/installing/installing_bare_metal_ipi/ipi-install-installation-workflow.html#additional-resources_config) files are provided in ```install-config-sno-example.yaml``` and ```install-config-standard-example.yaml```.
55

66
The install config uses the same format as an IPI install, except that it also requires you to set clusterImageSet. The example shows how to point the clusterImageSet to a mirror registry.
77

@@ -17,7 +17,7 @@ Finally, you can set a path to a folder containing scripts to be executed after
1717
```
1818
postInstallScriptsFolder: post_scripts
1919
```
20-
Other options are documented in ```install-config-sno-example.yaml```, ```install-config-standard-example.yaml``` and ```install-config-hypershift-example.yaml```.
20+
Other options are documented in ```install-config-sno-example.yaml``` and ```install-config-standard-example.yaml```.
2121

2222
---
2323
To run the playbook:

edge/docs/HYPERSHIFT.md

Lines changed: 0 additions & 14 deletions
This file was deleted.

edge/install-config-hypershift-example.yaml

Lines changed: 0 additions & 78 deletions
This file was deleted.
Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,5 @@
11
install_overrides: {}
2-
hypershift_configuration: {}
32
worker_count: 0
43
interface_number: 3
54
relocatable_ipv4_subnet: "192.168.7.0/24"
65
relocatable_ipv6_subnet: "fd04::/64"
7-
hypershift: false

edge/roles/edge_install/tasks/hypershift.yaml

Lines changed: 0 additions & 158 deletions
This file was deleted.

edge/roles/edge_install/tasks/main.yaml

Lines changed: 2 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -28,13 +28,6 @@
2828
register: k8s_result
2929
until: k8s_result is not failed
3030

31-
- name: Enable HyperShift
32-
when:
33-
- edgeCluster.hypershift is defined
34-
- edgeCluster.hypershift.enabled
35-
ansible.builtin.set_fact:
36-
hypershift: true
37-
3831
# these manifests are applied early in the install process, often they are MachineConfigs, applying them early helps avoid extra reboots
3932
- name: Create user-defined manifest config maps
4033
when: edgeCluster.installManifestsFolder is defined
@@ -63,13 +56,8 @@
6356
when: edgeCluster.reservedCpuSet is defined
6457
ansible.builtin.include_tasks: workload_partitioning.yaml
6558

66-
- name: Standard cluster install
67-
when: not hypershift
68-
ansible.builtin.include_tasks: standard.yaml
69-
70-
- name: HyperShift install
71-
when: hypershift
72-
ansible.builtin.include_tasks: hypershift.yaml
59+
- name: Cluster install
60+
ansible.builtin.include_tasks: install.yaml
7361
rescue:
7462
- name: Delete ClusterImageSet
7563
kubernetes.core.k8s:

edge/roles/edge_install/templates/ConfigMap.yaml.j2

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,5 @@ metadata:
44
name: "manifest-{{ idx }}"
55
namespace: "{{ metadata.name }}"
66
data:
7-
{% if not hypershift %}
87
{{ item | basename }}: |
9-
{% else %}
10-
config: |
11-
{% endif %}
128
{{ lookup('ansible.builtin.file', lookup('ansible.builtin.vars', 'item')) | indent(4) }}

0 commit comments

Comments
 (0)