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

Gen3 Monthly Release 2023.03 caninedc.org 1678210626 #5808

Closed

Conversation

PlanXCyborg
Copy link
Contributor

Applying version 2023.03 to caninedc.org

@PlanXCyborg PlanXCyborg requested review from trevars and a team as code owners March 7, 2023 17:37
@PlanXCyborg
Copy link
Contributor Author

caninedc.org

❌ etlMapping.yaml - gitops.json mismatch

  • Field error: Field [node_id] in explorerConfig.charts not found in etlMapping

@PlanXCyborg
Copy link
Contributor Author

caninedc.org/manifest.json

Deployment changes

  • fence
  • metadata
  • peregrine
    • Peregrine does not rely on configuration files in the cloud-automation repository anymore. The Peregrine configuration files are in the Peregrine repository. (PXP-10163 Python 3.9 peregrine#191)
  • sheepdog
  • sower.container.image.pelican-export
    • The Pelican export job should now be deployed alongside the metadata-delete-expired-objects cronjob: add "metadata-delete-expired-objects": "quay.io/cdis/metadata-delete-expired-objects:<version>" to the versions block of the manifest, run gen3 kube-setup-metadata-delete-expired-objects-cronjob and grant the metadata-delete-expired-objects-job client access to (resource=/mds_gateway, method=access, service=mds_gateway) and (resource=/programs, method=delete, service=fence) in the user.yaml. (PXP-10558 Pelican export: store PFB file's _expires_at in MDS pelican#69)

Breaking changes

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.

2 participants