Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Airgap Rancher Airgap Harvester Ansible Driver Playbook #400

Draft
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

irishgordo
Copy link

@irishgordo irishgordo commented Jan 9, 2023

  • introduces Ansible yaml that creates isolation from previous CI
    Ansible workload
  • new Ansible CI provides deeper flexibility to condition Ansible
    driving factors for Harvester-Installer while not altering previous CI
    infrastructure / Ansible Playbook

@irishgordo irishgordo force-pushed the feat/airgap-harvester-airgap-rancher-install-test branch 2 times, most recently from 769ae8d to 20c79d5 Compare June 30, 2023 18:37
@irishgordo irishgordo changed the title [WIP] Airgap Rancher Airgap Harvester Ansible Driver Airgap Rancher Airgap Harvester Ansible Driver Playbook Jun 30, 2023
@irishgordo irishgordo marked this pull request as ready for review June 30, 2023 18:39
* introduces Ansible yaml that creates isolation from previous CI
  Ansible workload
* new Ansible CI provides deeper flexibility to condition Ansible
  driving factors for Harvester-Installer while not altering previous CI
  infrastructure / Ansible Playbook

Resolves: feat/airgap-harvester-airgap-rancher-install-test
@irishgordo irishgordo force-pushed the feat/airgap-harvester-airgap-rancher-install-test branch from 20c79d5 to 99aff1b Compare June 30, 2023 18:41
@irishgordo irishgordo requested a review from a team June 30, 2023 22:54
@irishgordo irishgordo marked this pull request as draft January 5, 2024 19:53
@irishgordo
Copy link
Author

irishgordo commented Jan 5, 2024

Converted back to draft as:
#618
Was merged in - this should be re-adjusted or reworked.

This is currently leveraged still for daily-runs, but the system is not the most stable.

We're continuing to encounter some "occasional" issues with:

  • resources on the node running the job is inadequate, running 4 Harvester Nodes Virtualized w/ Docker-Registry, Rancher K3s, and other elements all virtualized as well 'airgapped' on a single node, will occasionally just fail due to resources on the machine not being enough
  • acquisition of Rancher dependent images occasionally just 'fail', most commonly jetstack based images, since docker-registry gets rebuilt and not persisted between runs
  • Rancher will occasionally just time out waiting for rollout to finish, retry logic is not geared for exponential backoff currently, but failures seem to be associated again with resource issues on the node

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant