openshift/installer
1
0
Fork 0
mirror of https://github.com/openshift/installer.git synced 2026-02-05 06:46:36 +01:00
Code Issues Releases Activity
Files
1dacae5d2db8b75560c8bdb3c1000338a65672ad
installer/go.mod

387 lines
20 KiB
Modula-2
Raw Normal View History

Add go.mod
2020-02-14 00:00:06 +01:00
module github.com/openshift/installer
bump(ocp/api): pull in updated DualReplica bumped ocp api to pull in DualReplica being promoted to TechPreview needed to pin apimachinery to kube 32 since bumping to kube 33 caused a dependency on cluster-api 1.11 which is currently in beta Signed-off-by: ehila <ehila@redhat.com>
2025-07-28 11:55:14 -04:00
go 1.24.0
go.mod: bump openshift/api to latest version Notice that we had to also bump machine-api-operator to include [1] so it would build with the latest openshift/api. [1] https://github.com/openshift/machine-api-operator/pull/1256
2024-07-03 10:38:28 +02:00
bump(ocp/api): pull in updated DualReplica bumped ocp api to pull in DualReplica being promoted to TechPreview needed to pin apimachinery to kube 32 since bumping to kube 33 caused a dependency on cluster-api 1.11 which is currently in beta Signed-off-by: ehila <ehila@redhat.com>
2025-07-28 11:55:14 -04:00
toolchain go1.24.5
Add go.mod
2020-02-14 00:00:06 +01:00
require (
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
cloud.google.com/go/kms v1.22.0
cloud.google.com/go/monitoring v1.24.2
cloud.google.com/go/storage v1.57.0
vendor: Bump github.com/AlecAivazis/survey The new version introduces prompting descriptions for multiple-choice selectors.
2022-07-04 12:14:23 +02:00
github.com/AlecAivazis/survey/v2 v2.3.5
go: update modules Signed-off-by: Vince Prignano <vincepri@redhat.com>
2023-10-31 08:01:50 -07:00
github.com/Azure/azure-sdk-for-go v68.0.0+incompatible
Update cluster-api-provide-azure to v1.21.1
2025-11-03 14:32:44 -05:00
github.com/Azure/azure-sdk-for-go/sdk/azcore v1.19.1
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/Azure/azure-sdk-for-go/sdk/azidentity v1.13.0
vendor: Azure packages for identity creation This revendors the azure packages that are needed to create a user-assigned identity.
2025-05-19 15:59:14 -04:00
github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/authorization/armauthorization/v3 v3.0.0-beta.2
Azure: go mod tidy
2024-02-14 10:53:17 -08:00
github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/compute/armcompute/v4 v4.2.1
Revert "Merge pull request #9665 from patrickdillon/revert-azurestack-ipi" This reverts commit 2d3f2c5763e99dce3d4e260a9270c222d7759466, reversing changes made to 63e0c358e0cd31b97d935b827975a748f9bc2360.
2025-04-16 10:06:31 -04:00
github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/compute/armcompute/v5 v5.7.0
vendor: Added armdns latest version Adding latest armdns version to create DNS entries.
2024-02-19 14:09:16 -05:00
github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/dns/armdns v1.2.0
Update cluster-api-provide-azure to v1.21.1
2025-11-03 14:32:44 -05:00
github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/keyvault/armkeyvault v1.5.0
github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/msi/armmsi v1.3.0
Update cluster-api-provider-azure to release-1.17.5 This will bring in the fix: kubernetes-sigs/cluster-api-provider-azure#5497
2025-03-25 10:01:53 -04:00
github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/network/armnetwork v1.1.0
go.mod: add azure armnetwork Adds armnetwork packages, for working with load balancers.
2024-03-28 19:12:23 -04:00
github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/network/armnetwork/v2 v2.2.1
go.mod: Bump CAPZ and ASO Bumps CAPZ to v1.19.3 and ASO to v2.11.0. Updates go.mod requires and go mod tidy for top-level go.mod, cluster-api/providers/azure(aso).
2025-05-12 10:14:48 -04:00
github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/privatedns/armprivatedns v1.3.0
add azure resourcegraph pkg
2023-11-17 13:12:27 +01:00
github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/resourcegraph/armresourcegraph v0.8.2
azure: Update capz version Updating capz version from v1.11.0 to v1.14.2
2024-04-15 10:23:58 -04:00
github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/resources/armresources v1.2.0
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/storage/armstorage v1.8.1
github.com/Azure/azure-sdk-for-go/sdk/storage/azblob v1.6.2
go.mod: Bump CAPZ and ASO Bumps CAPZ to v1.19.3 and ASO to v2.11.0. Updates go.mod requires and go mod tidy for top-level go.mod, cluster-api/providers/azure(aso).
2025-05-12 10:14:48 -04:00
github.com/Azure/go-autorest/autorest v0.11.30
Pin terraform-provider-azurerm to 2.48.0-openshift
2021-04-27 16:37:41 -04:00
github.com/Azure/go-autorest/autorest/to v0.4.0
power vs installconfig assets: vendoring a seperate commit for the vendor updates Signed-off-by: Christy Norman <christy@linux.vnet.ibm.com>
2022-03-03 12:33:15 -06:00
github.com/IBM-Cloud/bluemix-go v0.0.0-20211102075456-ffc4e11dfb16
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/IBM-Cloud/power-go-client v1.12.0
github.com/IBM/go-sdk-core/v5 v5.21.0
github.com/IBM/ibm-cos-sdk-go v1.12.3
DNM: Update go mod DO NOT MERGE: Update the go mod for BYOK support. Replace with proper upstream releases, rather than personal branches.
2023-11-29 12:05:55 -06:00
github.com/IBM/keyprotect-go-client v0.12.2
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/IBM/networking-go-sdk v0.51.11
github.com/IBM/platform-services-go-sdk v0.86.1
github.com/IBM/vpc-go-sdk v0.71.1
Go modules
2020-10-19 11:20:18 +03:00
github.com/apparentlymart/go-cidr v1.1.0
Add go.mod
2020-02-14 00:00:06 +01:00
github.com/awalterschulze/gographviz v0.0.0-20190522210029-fa59802746ab
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/aws/aws-sdk-go v1.55.7
github.com/aws/aws-sdk-go-v2 v1.39.2
github.com/aws/aws-sdk-go-v2/config v1.31.12
github.com/aws/aws-sdk-go-v2/credentials v1.18.16
github.com/aws/aws-sdk-go-v2/service/ec2 v1.233.0
deps: add missing aws sdk v2 packages The following services are added: - github.com/aws/aws-sdk-go-v2/service/elasticloadbalancingv2 - github.com/aws/aws-sdk-go-v2/service/elasticloadbalancing - github.com/aws/aws-sdk-go-v2/service/resourcegroupstaggingapi
2025-08-12 10:36:36 -07:00
github.com/aws/aws-sdk-go-v2/service/elasticloadbalancingv2 v1.49.0
Revert "Merge pull request #9736 from barbacbd/CORS-4058" This reverts commit 4e8d67e7dd811e8d5715b6d30d7c978be6041947, reversing changes made to d772abf0009d088cba4ad6d2ac4a3d57d96f6345.
2025-07-13 11:30:07 -04:00
github.com/aws/aws-sdk-go-v2/service/iam v1.32.0
OCPBUGS-47681: Support regions only available in v2 of the aws sdk ** update vendor
2025-02-05 11:51:36 -05:00
github.com/aws/aws-sdk-go-v2/service/route53 v1.48.6
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/aws/aws-sdk-go-v2/service/s3 v1.88.4
github.com/aws/aws-sdk-go-v2/service/sts v1.38.6
github.com/aws/smithy-go v1.23.0
vendor: add testscript
2022-11-14 03:22:43 -05:00
github.com/cavaliercoder/go-cpio v0.0.0-20180626203310-925f9528c45e
*: Migrate to ignition config spec v3.1 The installer now generates spec v3.1 ignition config, instead of v2.2 (and v2.4 for openstack) as before. The v3.1 ignition config specification can be found at [1]. A detailed overview of the differences between specs v2 and v3 can be found at [2]. Notable differences are: - the `Filesystem` identifier on ignition file configs no longer exists - `Overwrite` now defaults to `false` (was `true` in spec v2), which is why it is now set explicitly to keep the same behaviour. - duplicate file configs are now prohibited, i.e. all contents and all appendices must be defined in a single config. - duplicate systemd unit configs are now prohibited, i.e. the content and all dropins must be defined in a single config. This commit: - Bumps ignition to v2.3.0 with support for config spec v3.1. - Bumps terraform-provider-ignition to v2.1.0. Also adds downloading of the provider binary to `images/installer/Dockerfile.upi.ci` which is necessary because the ignition v2/spec3 version from the `community-terraform-providers/terraform-ignition-provider` fork is not present in the provider registry that is maintained by Hashicorp and can therefore not be pulled in automatically by terraform. is not present in the - Bumps machine-config-operator to b3b074ee9156 (latest commit at the time of this writing). - Adds "github.com/clarketm/json" dependency for marshaling Ignition configs. This is a dropin replacement for "encoding/json" that supports zero values of structs with omittempty annotations when marshaling. In effect, this will exclude empty pointer struct fields from the marshaled data instead of inserting nil values into them, which do not pass openAPI validation on fields that are supposed to contain e.g. strings. The same library is used by machine-config-operator and ignition itself. - Updates the vendor dir to make commit idempotent. [1] https://github.com/coreos/ignition/blob/master/doc/configuration-v3_1.md [2] https://github.com/coreos/ignition/blob/master/doc/migrating-configs.md#from-version-230-to-300 Co-authored-by: Vadim Rutkovsky <vrutkovs@redhat.com>
2020-07-21 18:39:41 +02:00
github.com/clarketm/json v1.14.1
OCPBUGS-34037: bump github.com/container/images for CVE fix
2024-06-10 18:35:14 +02:00
github.com/containers/image/v5 v5.31.0
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/coreos/ignition/v2 v2.24.0
go.mod: pull in new stream metadata & arm compute packages go get github.com/coreos/stream-metadata-go@main
2025-08-18 16:15:39 -04:00
github.com/coreos/stream-metadata-go v0.4.10-0.20250806142651-4a7d280a6c7b
Bump api, client-go, library-go for k8s 1.31
2024-10-02 13:25:26 -04:00
github.com/daixiang0/gci v0.13.4
libvirt: Use static libvirt library to destroy cluster When we create the cluster, the terraform provider uses a static pure-golang library to communicate with libvirt. Use the same library to destroy the cluster, instead of using one that has to dynamically link with the C library.
2023-06-16 11:12:48 +12:00
github.com/digitalocean/go-libvirt v0.0.0-20240220204746-fcabe97a6eed
AGENT-702: Generate minimal ISO for external platform - Renamed `ipxeBaseURL` to more generic `bootArtifactsBaseURL` - Removed unwanted lint - Added integration tests to create minimal ISO for external platform with and without bootArtifactsBaseURL in agent-config.yaml - Fixed existing integration tests to include change of name from `ipxeBaseURL` to more generic `bootArtifactsBaseURL` - Added BootArtifactsBaseUrl and bootArtifactsPath into parent asset AgentArtifacts - AgentArtifacts also depends on AgentConfig asset - Moved common code to generate rootfs.img file into extractRootFS() in AgentArtifacts asset - If the bootArtifactsBaseURL is specified, construct the custom rootfs URL otherwise default to the URL from the RHCOS streams file - For external platform when the bootArtifactsBaseUrl is specified, output the rootfs file alongside the minimal ISO - For all other platforms, continue generating full ISO (no explicit rootfs.img is generated) - Vendor changes after updating github.com/openshift/assisted-image-service dependency - set IMAGE_TYPE_ISO to 'minimal-iso' in create-cluster-and-infraenv.service.template when using external platform - Log an info message to upload CCM manifests Signed-off-by: Pawan Pinjarkar <ppinjark@redhat.com>
2023-08-28 12:19:42 -04:00
github.com/diskfs/go-diskfs v1.4.0
Vendor changes
2022-05-06 05:52:41 +00:00
github.com/form3tech-oss/jwt-go v3.2.3+incompatible
Update cluster-api-provide-azure to v1.21.1
2025-11-03 14:32:44 -05:00
github.com/go-logr/logr v1.4.3
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/go-openapi/errors v0.22.1
Move common code into NewCluster() method
2024-06-24 11:52:26 -04:00
github.com/go-openapi/runtime v0.28.0
PowerVS: Vendoring go.* changes
2024-03-25 15:44:05 -05:00
github.com/go-openapi/strfmt v0.23.0
Update cluster-api-provide-azure to v1.21.1
2025-11-03 14:32:44 -05:00
github.com/go-openapi/swag v0.23.1
OCPBUGS-41834: Add agent installer checks for hosts interface table Add checks for the host interface table to validate: - at least one entry is defined in the interface table when using network configuration - the MAC addresses in the interface table are using the expected format
2024-09-24 10:52:02 -04:00
github.com/go-openapi/validate v0.24.0
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/go-playground/validator/v10 v10.26.0
Update cluster-api-provide-azure to v1.21.1
2025-11-03 14:32:44 -05:00
github.com/golang-jwt/jwt/v4 v4.5.2
go.mod: Bump CCO for permission fix CCO was requiring the `s3:HeadBucket` permission which doesn't actually exist. The issue has been fixed in the lasted version.
2024-04-04 21:21:42 +02:00
github.com/golang/protobuf v1.5.4
Bump IBM Cloud CAPI commit
2025-03-31 23:47:21 -05:00
github.com/google/go-cmp v0.7.0
CORS-3188: bump k8s dependencies
2024-01-31 21:55:05 +01:00
github.com/google/uuid v1.6.0
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/googleapis/gax-go/v2 v2.15.0
github.com/gophercloud/gophercloud/v2 v2.8.0
deps: Bump Gophercloud to v2.5.0 This dependency bump enables batch security group rule creation in OpenStack.
2024-12-18 13:59:21 +01:00
github.com/gophercloud/utils/v2 v2.0.0-20250212084022-725b94822eeb
cache: Support artifacts compressed with xz Switches to "github.com/h2non/filetype/matchers" for MIME type matching and uses "github.com/ulikunitz/xz" for xz decompression.
2020-02-27 22:56:18 +01:00
github.com/h2non/filetype v1.0.12
Inline staticnetworkconfig from assisted-service In later versions of assisted-service, this code changes from shelling out to nmstatectl and instead uses the libnmstate library. Since we don't have a way of building with that yet, this is preventing us from updating assisted-service. Move the nmstatectl-based implementation in-tree so we can continue to use it independently of assisted-service.
2023-08-21 16:44:41 +12:00
github.com/hashicorp/go-multierror v1.1.1
vendoring: bump gophercloud, CAPO and deps * Update go.mod to have CAPO v0.11.1 (latest) * `go mod tidy && go mod vendor`
2024-10-29 15:35:27 -04:00
github.com/hashicorp/go-version v1.7.0
** Vendor updates to include httpmock for tests.
2025-02-27 10:08:08 -05:00
github.com/jarcoal/httpmock v1.3.1
go: update modules Signed-off-by: Vince Prignano <vincepri@redhat.com>
2023-10-31 08:01:50 -07:00
github.com/jongio/azidext/go/azidext v0.5.0
Add a dependency on Nutanix machine api provider Check in the vendored dependency.
2022-03-16 21:09:11 +01:00
github.com/kdomanski/iso9660 v0.2.1
METAL-803: Update vendoring for baremetal-operator Required for RAID config Removes local_gb from terraform properties as its not required and no longer part of the BMO api. Sets to cpu_arch to x86_64 as this is all that is supported by the installer(and its no longer part of the BMO api).
2023-12-07 09:17:16 +00:00
github.com/metal3-io/baremetal-operator/apis v0.4.0
github.com/metal3-io/baremetal-operator/pkg/hardwareutils v0.4.0
go.mod: Bump CCO for permission fix CCO was requiring the `s3:HeadBucket` permission which doesn't actually exist. The issue has been fixed in the lasted version.
2024-04-04 21:21:42 +02:00
github.com/microsoft/kiota-authentication-azure-go v0.6.0
github.com/microsoftgraph/msgraph-sdk-go v0.59.0
Upgrading cluster-api-provider-nutanix version to 1.7.0
2025-08-06 12:00:42 +05:30
github.com/nutanix-cloud-native/cluster-api-provider-nutanix v1.7.0
OCPBUGS-48044: [Nutanix] upgrade vendoring for cluster-api-provider-nutanix
2025-01-30 15:45:18 -05:00
github.com/nutanix-cloud-native/prism-go-client v0.5.0
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/onsi/gomega v1.38.2
Bump openshift/api Pulling in the internalDNSRecords field from https://github.com/openshift/api/pull/2460
2025-11-17 15:44:37 -06:00
github.com/openshift/api v0.0.0-20251117165054-348370f055bf
MULTIARCH-4515: Add new files for agent-based installer (LPAR support for s390x)staller Add LPAR support for agend-based installer and bump version. Signed-off-by: Amadeus Podvratnik <apodvrat@redhat.com>
2024-06-06 16:09:14 +02:00
github.com/openshift/assisted-image-service v0.0.0-20240607085136-02df2e56dde6
Update assisted-service vendoring Update to the assisted-service at commit a40422bdea617f16cbdb724d53619ca74773be45. This repo now contains multiple go modules, so we have to add overrides for the internal references to the api and models modules.
2022-09-28 17:04:01 -04:00
github.com/openshift/assisted-service/api v0.0.0
Update to latest assisted-service With the assisted-service client now in a separate go module, we are able to drop the dependency on the main assisted-service module. This allows us to update to the latest version without pulling in any undesirable dependencies as a side-effect.
2023-08-22 22:17:27 +12:00
github.com/openshift/assisted-service/client v0.0.0
Update assisted-service vendoring Update to the assisted-service at commit a40422bdea617f16cbdb724d53619ca74773be45. This repo now contains multiple go modules, so we have to add overrides for the internal references to the api and models modules.
2022-09-28 17:04:01 -04:00
github.com/openshift/assisted-service/models v0.0.0
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/openshift/client-go v0.0.0-20251015124057-db0dee36e235
go.mod: Bump CCO for permission fix CCO was requiring the `s3:HeadBucket` permission which doesn't actually exist. The issue has been fixed in the lasted version.
2024-04-04 21:21:42 +02:00
github.com/openshift/cloud-credential-operator v0.0.0-20240404165937-5e8812d64187
Break dependency to cluster-api-aws provider, bump opensift/api, revendor AWSMachines was moved to openshift/api Also bump govmomi version along, due to go 1.16 dependency resolution
2022-04-12 13:27:30 +02:00
github.com/openshift/cluster-api-provider-baremetal v0.0.0-20220408122422-7a548effc26e
Update `cluster-api-provider-libvirt` and remove `github.com/ghodss/yaml` Reference: https://github.com/openshift/cluster-api-provider-libvirt/pull/252 Signed-off-by: Eng Zer Jun <engzerjun@gmail.com>
2023-03-09 00:35:28 +08:00
github.com/openshift/cluster-api-provider-libvirt v0.2.1-0.20230308152226-83c0473d4429
ovirt: preallocated disks This change adds support for creating preallocated disks in oVirt. Fixes BZ 2056460
2022-02-16 20:29:04 +01:00
github.com/openshift/cluster-api-provider-ovirt v0.1.1-0.20220323121149-e3f2850dd519
MGMT-18292: in order to be able to import openshift installer we need to update assisted service as it requires new hive
2024-09-26 17:12:16 +03:00
github.com/openshift/hive/apis v0.0.0-20231220215202-ad99b9e52d27
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/openshift/library-go v0.0.0-20251107090138-0de9712313a5
Vendor updates for GCP Machine API Provider
2024-10-21 15:21:14 -04:00
github.com/openshift/machine-api-provider-gcp v0.0.1-0.20241021180644-0eca0846914a
CORS-2934: IBMCloud: Update MAPI for BYOK Update the IBM MAPI base to pull in changes to MachineSpec for BYOK support. Related: https://issues.redhat.com/browse/CORS-2934
2023-12-07 11:26:19 -06:00
github.com/openshift/machine-api-provider-ibmcloud v0.0.0-20231207164151-6b0b8ea7b16d
Update dependencies go mod tidy && go mod vendor
2022-04-25 20:21:49 -04:00
github.com/ovirt/go-ovirt v0.0.0-20210809163552-d4276e35d3db
Update assisted-service vendoring Update to the assisted-service at commit a40422bdea617f16cbdb724d53619ca74773be45. This repo now contains multiple go modules, so we have to add overrides for the internal references to the api and models modules.
2022-09-28 17:04:01 -04:00
github.com/pelletier/go-toml v1.9.5
vendor: add testscript
2022-11-14 03:22:43 -05:00
github.com/pkg/diff v0.0.0-20210226163009-20ebb0f2a09e
Add go.mod
2020-02-14 00:00:06 +01:00
github.com/pkg/errors v0.9.1
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/pkg/sftp v1.13.10
github.com/prometheus/client_golang v1.23.2
github.com/prometheus/common v0.66.1
github.com/rogpeppe/go-internal v1.14.1
Add go.mod
2020-02-14 00:00:06 +01:00
github.com/shurcooL/vfsgen v0.0.0-20181202132449-6a9ea43bcacd
Update assisted-image-service
2023-07-04 15:43:48 +12:00
github.com/sirupsen/logrus v1.9.3
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/spf13/cobra v1.10.1
Update cluster-api-provide-azure to v1.21.1
2025-11-03 14:32:44 -05:00
github.com/stretchr/testify v1.11.1
Add retry package
2022-07-21 12:10:37 -04:00
github.com/thedevsaddam/retry v0.0.0-20200324223450-9769a859cc6d
MGMT-19191: Provide a way to add coreos installer params for installation phase Adding new field CoreosInstallerParams to image based install command to customize coreos installer command in lca cli
2024-10-28 12:49:51 +02:00
github.com/thoas/go-funk v0.9.3
OCPBUGS-34037: bump github.com/container/images for CVE fix
2024-06-10 18:35:14 +02:00
github.com/ulikunitz/xz v0.5.12
Update dependencies go mod tidy && go mod vendor
2022-04-25 20:21:49 -04:00
github.com/vincent-petithory/dataurl v1.0.0
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/vmware/govmomi v0.51.0
go.uber.org/mock v0.6.0
golang.org/x/crypto v0.43.0
golang.org/x/oauth2 v0.32.0
golang.org/x/sync v0.17.0
golang.org/x/sys v0.37.0
golang.org/x/term v0.36.0
golang.org/x/text v0.30.0
google.golang.org/api v0.252.0
google.golang.org/genproto/googleapis/api v0.0.0-20250825161204-c5933d9347a5
google.golang.org/grpc v1.76.0
go: update modules Signed-off-by: Vince Prignano <vincepri@redhat.com>
2023-10-31 08:01:50 -07:00
gopkg.in/ini.v1 v1.67.0
Update MAO depedencies This commit updates various MAO dependencies.
2020-11-30 18:56:22 -05:00
gopkg.in/yaml.v2 v2.4.0
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
k8s.io/api v0.34.1
k8s.io/apiextensions-apiserver v0.34.1
k8s.io/apimachinery v0.34.1
k8s.io/client-go v0.34.1
Bump api, client-go, library-go for k8s 1.31
2024-10-02 13:25:26 -04:00
k8s.io/cloud-provider-vsphere v1.31.0
go.mod Update
2020-10-22 11:01:37 -04:00
k8s.io/klog v1.0.0
Bump api, client-go, library-go for k8s 1.31
2024-10-02 13:25:26 -04:00
k8s.io/klog/v2 v2.130.1
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
k8s.io/utils v0.0.0-20250820121507-0af2bda4dd1d
baremetal: vendor libvirtxml
2024-04-08 14:22:40 -03:00
libvirt.org/go/libvirtxml v1.10002.0
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
sigs.k8s.io/cluster-api v1.11.2
Bump version of capi-provider-aws to 17a09f59176ca6c80208768ddd8e7cb6f75a2155
2025-04-11 14:30:55 -03:00
sigs.k8s.io/cluster-api-provider-aws/v2 v2.7.1-0.20250314180547-17a09f59176c
Update cluster-api-provide-azure to v1.21.1
2025-11-03 14:32:44 -05:00
sigs.k8s.io/cluster-api-provider-azure v1.21.1
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
sigs.k8s.io/cluster-api-provider-gcp v1.10.1-0.20251030112604-5c2bfd5aadb3
sigs.k8s.io/cluster-api-provider-ibmcloud v0.12.0
sigs.k8s.io/cluster-api-provider-openstack v0.13.0
sigs.k8s.io/cluster-api-provider-vsphere v1.14.0
sigs.k8s.io/controller-runtime v0.22.1
Vendor updates for GCP Machine API Provider
2024-10-21 15:21:14 -04:00
sigs.k8s.io/controller-tools v0.16.3
Bump api to latest master
2025-03-17 09:10:46 +01:00
sigs.k8s.io/json v0.0.0-20241014173422-cfa47c3a1cc8
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
sigs.k8s.io/yaml v1.6.0
Add go.mod
2020-02-14 00:00:06 +01:00
)
go.mod: pull in new stream metadata & arm compute packages go get github.com/coreos/stream-metadata-go@main
2025-08-18 16:15:39 -04:00
require (
github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/compute/armcompute v1.0.0
github.com/aws/aws-sdk-go-v2/service/resourcegroupstaggingapi v1.29.0
)
deps: add missing aws sdk v2 packages The following services are added: - github.com/aws/aws-sdk-go-v2/service/elasticloadbalancingv2 - github.com/aws/aws-sdk-go-v2/service/elasticloadbalancing - github.com/aws/aws-sdk-go-v2/service/resourcegroupstaggingapi
2025-08-12 10:36:36 -07:00
deps: add servicequotas v2 package
2025-08-15 00:33:23 -07:00
require github.com/aws/aws-sdk-go-v2/service/servicequotas v1.31.0
Update cluster-api-provide-azure to v1.21.1
2025-11-03 14:32:44 -05:00
require (
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
cel.dev/expr v0.24.0 // indirect
github.com/GoogleCloudPlatform/opentelemetry-operations-go/detectors/gcp v1.29.0 // indirect
github.com/GoogleCloudPlatform/opentelemetry-operations-go/exporter/metric v0.53.0 // indirect
github.com/GoogleCloudPlatform/opentelemetry-operations-go/internal/resourcemapping v0.53.0 // indirect
github.com/cncf/xds/go v0.0.0-20250501225837-2ac532fd4443 // indirect
github.com/envoyproxy/go-control-plane/envoy v1.32.4 // indirect
github.com/envoyproxy/protoc-gen-validate v1.2.1 // indirect
Update cluster-api-provide-azure to v1.21.1
2025-11-03 14:32:44 -05:00
github.com/evanphx/json-patch v5.9.11+incompatible // indirect
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/go-jose/go-jose/v4 v4.1.2 // indirect
github.com/planetscale/vtprotobuf v0.6.1-0.20240319094008-0393e58bdf10 // indirect
github.com/spiffe/go-spiffe/v2 v2.5.0 // indirect
github.com/zeebo/errs v1.4.0 // indirect
go.opentelemetry.io/contrib/detectors/gcp v1.36.0 // indirect
go.opentelemetry.io/otel/sdk v1.38.0 // indirect
go.opentelemetry.io/otel/sdk/metric v1.38.0 // indirect
go.yaml.in/yaml/v2 v2.4.2 // indirect
go.yaml.in/yaml/v3 v3.0.4 // indirect
golang.org/x/tools/go/expect v0.1.0-deprecated // indirect
golang.org/x/tools/godoc v0.1.0-deprecated // indirect
sigs.k8s.io/structured-merge-diff/v6 v6.3.0 // indirect
Update cluster-api-provide-azure to v1.21.1
2025-11-03 14:32:44 -05:00
)
Revendor with golang 1.17
2021-11-24 00:43:52 -05:00
require (
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
cloud.google.com/go v0.121.6 // indirect
cloud.google.com/go/auth v0.17.0 // indirect
cloud.google.com/go/auth/oauth2adapt v0.2.8 // indirect
cloud.google.com/go/compute/metadata v0.9.0 // indirect
cloud.google.com/go/iam v1.5.3 // indirect
cloud.google.com/go/longrunning v0.6.7 // indirect
Update cluster-api-provide-azure to v1.21.1
2025-11-03 14:32:44 -05:00
github.com/Azure/azure-sdk-for-go/sdk/internal v1.11.2 // indirect
go: Adds CAPO as a dependency to the installer Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
2024-02-19 16:39:40 -03:00
github.com/Azure/go-ansiterm v0.0.0-20230124172434-306776ec8161 // indirect
Revendor with golang 1.17
2021-11-24 00:43:52 -05:00
github.com/Azure/go-autorest v14.2.0+incompatible // indirect
Update cluster-api-provider-azure to release-1.17.5 This will bring in the fix: kubernetes-sigs/cluster-api-provider-azure#5497
2025-03-25 10:01:53 -04:00
github.com/Azure/go-autorest/autorest/adal v0.9.24 // indirect
Revendor with golang 1.17
2021-11-24 00:43:52 -05:00
github.com/Azure/go-autorest/autorest/date v0.3.0 // indirect
github.com/Azure/go-autorest/autorest/validation v0.3.1 // indirect
github.com/Azure/go-autorest/logger v0.2.1 // indirect
github.com/Azure/go-autorest/tracing v0.6.0 // indirect
Update cluster-api-provide-azure to v1.21.1
2025-11-03 14:32:44 -05:00
github.com/AzureAD/microsoft-authentication-library-for-go v1.5.0 // indirect
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/BurntSushi/toml v1.4.1-0.20240526193622-a339e1f7089c // indirect
Import machine-api-provider-gcp util package.
2023-12-18 11:00:55 +01:00
github.com/MakeNowJust/heredoc v1.0.0 // indirect
Update Nutanix terraform version to 1.5.0 for installer The updated versions include bugfixes for various components.
2022-05-23 11:50:39 +02:00
github.com/PaesslerAG/gval v1.0.0 // indirect
github.com/PaesslerAG/jsonpath v0.1.1 // indirect
Vendoring changes platform-services-go-sdk to v0.42.0
2023-08-07 16:38:33 -05:00
github.com/asaskevich/govalidator v0.0.0-20230301143203-a9d515a09cc2 // indirect
go.mod: Bump CAPZ and ASO Bumps CAPZ to v1.19.3 and ASO to v2.11.0. Updates go.mod requires and go mod tidy for top-level go.mod, cluster-api/providers/azure(aso).
2025-05-12 10:14:48 -04:00
github.com/asaskevich/govalidator/v11 v11.0.2-0.20250122183457-e11347878e23 // indirect
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream v1.7.1 // indirect
github.com/aws/aws-sdk-go-v2/feature/ec2/imds v1.18.9 // indirect
github.com/aws/aws-sdk-go-v2/internal/configsources v1.4.9 // indirect
github.com/aws/aws-sdk-go-v2/internal/endpoints/v2 v2.7.9 // indirect
CORS-4060: Migrate AWS sdk to v2 in infrastructure ** Vendor updates
2025-05-30 16:04:35 -04:00
github.com/aws/aws-sdk-go-v2/internal/ini v1.8.3 // indirect
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/aws/aws-sdk-go-v2/internal/v4a v1.4.9 // indirect
deps: add missing aws sdk v2 packages The following services are added: - github.com/aws/aws-sdk-go-v2/service/elasticloadbalancingv2 - github.com/aws/aws-sdk-go-v2/service/elasticloadbalancing - github.com/aws/aws-sdk-go-v2/service/resourcegroupstaggingapi
2025-08-12 10:36:36 -07:00
github.com/aws/aws-sdk-go-v2/service/elasticloadbalancing v1.32.0
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/aws/aws-sdk-go-v2/service/internal/accept-encoding v1.13.1 // indirect
github.com/aws/aws-sdk-go-v2/service/internal/checksum v1.9.0 // indirect
github.com/aws/aws-sdk-go-v2/service/internal/presigned-url v1.13.9 // indirect
github.com/aws/aws-sdk-go-v2/service/internal/s3shared v1.19.9 // indirect
github.com/aws/aws-sdk-go-v2/service/sso v1.29.6 // indirect
github.com/aws/aws-sdk-go-v2/service/ssooidc v1.35.1 // indirect
Revendor with golang 1.17
2021-11-24 00:43:52 -05:00
github.com/beorn7/perks v1.0.1 // indirect
go: update modules Signed-off-by: Vince Prignano <vincepri@redhat.com>
2023-10-31 08:01:50 -07:00
github.com/blang/semver v3.5.1+incompatible // indirect
github.com/blang/semver/v4 v4.0.0 // indirect
go.mod: bump capa to latest version
2024-04-23 14:36:12 +02:00
github.com/cespare/xxhash/v2 v2.3.0 // indirect
Import machine-api-provider-gcp util package.
2023-12-18 11:00:55 +01:00
github.com/chai2010/gettext-go v1.0.2 // indirect
go.mod: Bump CCO for permission fix CCO was requiring the `s3:HeadBucket` permission which doesn't actually exist. The issue has been fixed in the lasted version.
2024-04-04 21:21:42 +02:00
github.com/cjlapao/common-go v0.0.39 // indirect
OCPBUGS-34037: bump github.com/container/images for CVE fix
2024-06-10 18:35:14 +02:00
github.com/containers/storage v1.54.0 // indirect
Add imagebased installation ISO assets Signed-off-by: Michail Resvanis <mresvani@redhat.com>
2024-07-03 09:48:44 +02:00
github.com/coreos/go-json v0.0.0-20230131223807-18775e0fb4fb // indirect
go: update modules Signed-off-by: Vince Prignano <vincepri@redhat.com>
2023-10-31 08:01:50 -07:00
github.com/coreos/go-semver v0.3.1 // indirect
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/coreos/go-systemd/v22 v22.6.0 // indirect
go: update modules Signed-off-by: Vince Prignano <vincepri@redhat.com>
2023-10-31 08:01:50 -07:00
github.com/coreos/vcontext v0.0.0-20230201181013-d72178a18687 // indirect
provision CAPI/CAPV controller
2024-01-30 09:50:36 -05:00
github.com/davecgh/go-spew v1.1.2-0.20180830191138-d8f796af33cc // indirect
OCPBUGS-34037: bump github.com/container/images for CVE fix
2024-06-10 18:35:14 +02:00
github.com/docker/go-units v0.5.0 // indirect
AGENT-702: Generate minimal ISO for external platform - Renamed `ipxeBaseURL` to more generic `bootArtifactsBaseURL` - Removed unwanted lint - Added integration tests to create minimal ISO for external platform with and without bootArtifactsBaseURL in agent-config.yaml - Fixed existing integration tests to include change of name from `ipxeBaseURL` to more generic `bootArtifactsBaseURL` - Added BootArtifactsBaseUrl and bootArtifactsPath into parent asset AgentArtifacts - AgentArtifacts also depends on AgentConfig asset - Moved common code to generate rootfs.img file into extractRootFS() in AgentArtifacts asset - If the bootArtifactsBaseURL is specified, construct the custom rootfs URL otherwise default to the URL from the RHCOS streams file - For external platform when the bootArtifactsBaseUrl is specified, output the rootfs file alongside the minimal ISO - For all other platforms, continue generating full ISO (no explicit rootfs.img is generated) - Vendor changes after updating github.com/openshift/assisted-image-service dependency - set IMAGE_TYPE_ISO to 'minimal-iso' in create-cluster-and-infraenv.service.template when using external platform - Log an info message to upload CCM manifests Signed-off-by: Pawan Pinjarkar <ppinjark@redhat.com>
2023-08-28 12:19:42 -04:00
github.com/elliotwutingfeng/asciiset v0.0.0-20230602022725-51bbb787efab // indirect
Upgrading cluster-api-provider-nutanix version to 1.7.0
2025-08-06 12:00:42 +05:30
github.com/emicklei/go-restful/v3 v3.12.2 // indirect
go.mod: Bump CAPZ and ASO Bumps CAPZ to v1.19.3 and ASO to v2.11.0. Updates go.mod requires and go mod tidy for top-level go.mod, cluster-api/providers/azure(aso).
2025-05-12 10:14:48 -04:00
github.com/evanphx/json-patch/v5 v5.9.11 // indirect
Update cluster-api-provide-azure to v1.21.1
2025-11-03 14:32:44 -05:00
github.com/exponent-io/jsonpath v0.0.0-20210407135951-1de76d718b3f // indirect
Vendor updates
2025-01-21 07:10:00 -05:00
github.com/fatih/color v1.18.0 // indirect
CORS-3212: CAPG Add ignition for CAPG machines ** update vendor to include google storage api
2024-02-28 14:07:45 -05:00
github.com/felixge/httpsnoop v1.0.4 // indirect
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/fxamacker/cbor/v2 v2.9.0 // indirect
github.com/gabriel-vasile/mimetype v1.4.9 // indirect
Import machine-api-provider-gcp util package.
2023-12-18 11:00:55 +01:00
github.com/go-errors/errors v1.4.2 // indirect
azure: update mod and vendor
2022-11-22 23:22:45 +01:00
github.com/go-logr/stdr v1.2.2 // indirect
CORS-3280: Bump cluster-api-provider-gcp to v1.6.0 Release notes are here https://github.com/kubernetes-sigs/cluster-api-provider-gcp/releases/tag/v1.6.0
2024-03-13 08:40:39 -04:00
github.com/go-logr/zapr v1.3.0 // indirect
OCPBUGS-34037: bump github.com/container/images for CVE fix
2024-06-10 18:35:14 +02:00
github.com/go-openapi/analysis v0.23.0 // indirect
Update cluster-api-provide-azure to v1.21.1
2025-11-03 14:32:44 -05:00
github.com/go-openapi/jsonpointer v0.21.1 // indirect
OCPBUGS-34037: bump github.com/container/images for CVE fix
2024-06-10 18:35:14 +02:00
github.com/go-openapi/jsonreference v0.21.0 // indirect
github.com/go-openapi/loads v0.22.0 // indirect
github.com/go-openapi/spec v0.21.0 // indirect
PowerVS: Vendoring changes Vendoring bump networking-go-sdk to v0.42.2 Include networking-go-sdk/transitgatewayapisv1
2023-07-25 14:08:18 -05:00
github.com/go-playground/locales v0.14.1 // indirect
github.com/go-playground/universal-translator v0.18.1 // indirect
Vendor updates
2025-01-21 07:10:00 -05:00
github.com/gobuffalo/flect v1.0.3 // indirect
Revert "Merge pull request #9665 from patrickdillon/revert-azurestack-ipi" This reverts commit 2d3f2c5763e99dce3d4e260a9270c222d7759466, reversing changes made to 63e0c358e0cd31b97d935b827975a748f9bc2360.
2025-04-16 10:06:31 -04:00
github.com/gofrs/uuid v4.4.0+incompatible // indirect
vendoring: bump gophercloud, CAPO and deps * Update go.mod to have CAPO v0.11.1 (latest) * `go mod tidy && go mod vendor`
2024-10-29 15:35:27 -04:00
github.com/gofrs/uuid/v5 v5.3.0 // indirect
Revendor with golang 1.17
2021-11-24 00:43:52 -05:00
github.com/gogo/protobuf v1.3.2 // indirect
Update cluster-api-provide-azure to v1.21.1
2025-11-03 14:32:44 -05:00
github.com/golang-jwt/jwt/v5 v5.3.0 // indirect
vendor: replace mockgen with go.uber.org/mock/gomock go mod tidy && go mod vendor Remove direct dependency on "github.com/golang/mock/mockgen"
2025-01-30 16:44:50 -05:00
github.com/golang/mock v1.7.0-rc.1 // indirect
Vendor updates
2025-02-05 13:25:45 -05:00
github.com/google/btree v1.1.3 // indirect
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/google/gnostic-models v0.7.0 // indirect
github.com/google/s2a-go v0.1.9 // indirect
Import machine-api-provider-gcp util package.
2023-12-18 11:00:55 +01:00
github.com/google/shlex v0.0.0-20191202100458-e7afc7fbc510 // indirect
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/googleapis/enterprise-certificate-proxy v0.3.6 // indirect
github.com/gorilla/websocket v1.5.4-0.20250319132907-e064f32e3674 // indirect
release checklist: bump k8s dependencies
2025-01-23 11:15:29 -08:00
github.com/gregjones/httpcache v0.0.0-20190611155906-901d90724c79 // indirect
OCPBUGS-27507: bump containerd for vulnerability fix
2024-01-23 18:03:12 +01:00
github.com/hashicorp/errwrap v1.1.0 // indirect
Upgrade to Terraform 0.14.6: update go.mod Update terraform-provider-aws to 3.1.0 Update terraform-provider-azure to 2.48.0 Update terraform-provider-google to 3.40.0
2021-03-10 19:13:42 -08:00
github.com/hashicorp/go-cleanhttp v0.5.2 // indirect
Update cluster-api-provide-azure to v1.21.1
2025-11-03 14:32:44 -05:00
github.com/hashicorp/go-retryablehttp v0.7.8 // indirect
tooling: vendor gci tool
2022-12-12 22:29:50 +01:00
github.com/hexops/gotextdiff v1.0.3 // indirect
go: update modules Signed-off-by: Vince Prignano <vincepri@redhat.com>
2023-10-31 08:01:50 -07:00
github.com/inconshreveable/mousetrap v1.1.0 // indirect
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/itchyny/gojq v0.12.9 // indirect
github.com/itchyny/timefmt-go v0.1.4 // indirect
Update dependencies go mod tidy && go mod vendor
2022-04-25 20:21:49 -04:00
github.com/jinzhu/inflection v1.0.0 // indirect
Update assisted-service vendoring Update to the assisted-service at commit a40422bdea617f16cbdb724d53619ca74773be45. This repo now contains multiple go modules, so we have to add overrides for the internal references to the api and models modules.
2022-09-28 17:04:01 -04:00
github.com/jinzhu/now v1.1.4 // indirect
Revendor with golang 1.17
2021-11-24 00:43:52 -05:00
github.com/jmespath/go-jmespath v0.4.0 // indirect
power vs installconfig assets: vendoring a seperate commit for the vendor updates Signed-off-by: Christy Norman <christy@linux.vnet.ibm.com>
2022-03-03 12:33:15 -06:00
github.com/josharian/intern v1.0.0 // indirect
vendor: update openshift/api to include some alibaba infra changes * Update openshift/api to 6e0b1eb97188. * Update kube modules to v0.23.0. * Update controller-runtime to v0.11.0. * Remove unused terraform-provider-kubernetes.
2021-12-17 14:18:12 -05:00
github.com/json-iterator/go v1.1.12 // indirect
Revendor with golang 1.17
2021-11-24 00:43:52 -05:00
github.com/kballard/go-shellquote v0.0.0-20180428030007-95032a82bc51 // indirect
github.com/kr/fs v0.1.0 // indirect
azure: azidentity: update go.mod and vendor Notice that azblob also had to be upgraded to 0.4.1, otherwise we hit the following build issue: vendor/github.com/Azure/azure-sdk-for-go/sdk/storage/azblob/zc_blob_lease_client.go:25:16: undefined: to.StringPtr vendor/github.com/Azure/azure-sdk-for-go/sdk/storage/azblob/zc_block_blob_client.go:145:20: undefined: to.StringPtr vendor/github.com/Azure/azure-sdk-for-go/sdk/storage/azblob/zc_container_lease_client.go:25:16: undefined: to.StringPtr vendor/github.com/Azure/azure-sdk-for-go/sdk/storage/azblob/zc_shared_policy_shared_key_credential.go:190:17: undefined: log.EventResponse vendor/github.com/Azure/azure-sdk-for-go/sdk/storage/azblob/zm_lease_request_options.go:63:16: undefined: to.StringPtr vendor/github.com/Azure/azure-sdk-for-go/sdk/storage/azblob/zm_lease_request_options.go:142:16: undefined: to.StringPtr and newer versions cause pkg/gather/azure/azure.go:224:29: undefined: azblob.NewBlobClientWithSharedKey pkg/gather/azure/azure.go:235:48: unknown field 'MaxRetryRequests' in struct literal of type blob.RetryReaderOptions
2022-10-04 23:55:12 +02:00
github.com/kylelemons/godebug v1.1.0 // indirect
PowerVS: Vendoring go.* changes
2024-03-25 15:44:05 -05:00
github.com/leodido/go-urn v1.4.0 // indirect
MGMT-18292: in order to be able to import openshift installer we need to update assisted service as it requires new hive
2024-09-26 17:12:16 +03:00
github.com/lib/pq v1.10.9 // indirect
Import machine-api-provider-gcp util package.
2023-12-18 11:00:55 +01:00
github.com/liggitt/tabwriter v0.0.0-20181228230101-89fcab3d43de // indirect
Update cluster-api-provide-azure to v1.21.1
2025-11-03 14:32:44 -05:00
github.com/mailru/easyjson v0.9.0 // indirect
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/mattn/go-colorable v0.1.14 // indirect
Vendoring changes
2024-02-26 09:32:20 -06:00
github.com/mattn/go-isatty v0.0.20 // indirect
CORS-3288: bump CAPA for LB scheme fix This makes it possible to have public subnets associated with an external secondary LB.
2024-03-06 22:22:25 +01:00
github.com/mgutz/ansi v0.0.0-20200706080929-d51e80ef957d // indirect
go.mod: Bump CCO for permission fix CCO was requiring the `s3:HeadBucket` permission which doesn't actually exist. The issue has been fixed in the lasted version.
2024-04-04 21:21:42 +02:00
github.com/microsoft/kiota-abstractions-go v0.18.0 // indirect
github.com/microsoft/kiota-http-go v0.16.0 // indirect
github.com/microsoft/kiota-serialization-form-go v0.9.0 // indirect
github.com/microsoft/kiota-serialization-json-go v0.9.0 // indirect
github.com/microsoft/kiota-serialization-text-go v0.7.0 // indirect
github.com/microsoftgraph/msgraph-sdk-go-core v0.34.1 // indirect
Import machine-api-provider-gcp util package.
2023-12-18 11:00:55 +01:00
github.com/mitchellh/go-wordwrap v1.0.1 // indirect
Add dependency on Nutanix Prism Go Client Use prism-go-client instead of embedded client in nutanix terraform provider for the installer.
2022-06-14 16:03:41 +02:00
github.com/mitchellh/mapstructure v1.5.0 // indirect
release checklist: bump k8s dependencies
2025-01-23 11:15:29 -08:00
github.com/moby/spdystream v0.5.0 // indirect
OCPBUGS-34037: bump github.com/container/images for CVE fix
2024-06-10 18:35:14 +02:00
github.com/moby/sys/mountinfo v0.7.1 // indirect
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/moby/sys/user v0.4.0 // indirect
OCPBUGS-34037: bump github.com/container/images for CVE fix
2024-06-10 18:35:14 +02:00
github.com/moby/term v0.5.0 // indirect
Revendor with golang 1.17
2021-11-24 00:43:52 -05:00
github.com/modern-go/concurrent v0.0.0-20180306012644-bacd9c7ef1dd // indirect
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/modern-go/reflect2 v1.0.3-0.20250322232337-35a7c28c31ee // indirect
Import machine-api-provider-gcp util package.
2023-12-18 11:00:55 +01:00
github.com/monochromegane/go-gitignore v0.0.0-20200626010858-205db1a8cc00 // indirect
Update kube components to v0.24.0 Update kube go dependencies to v0.24.0 releases along with updating the vendor files.
2022-07-25 15:03:21 -05:00
github.com/munnerz/goautoneg v0.0.0-20191010083416-a7dc8b61c822 // indirect
CORS-3188: bump k8s dependencies
2024-01-31 21:55:05 +01:00
github.com/mxk/go-flowrate v0.0.0-20140419014527-cca7078d478f // indirect
Revendor with golang 1.17
2021-11-24 00:43:52 -05:00
github.com/oklog/ulid v1.3.1 // indirect
github.com/opencontainers/go-digest v1.0.0 // indirect
OCPBUGS-34037: bump github.com/container/images for CVE fix
2024-06-10 18:35:14 +02:00
github.com/opencontainers/image-spec v1.1.0 // indirect
github.com/opencontainers/runtime-spec v1.2.0 // indirect
MGMT-18292: in order to be able to import openshift installer we need to update assisted service as it requires new hive
2024-09-26 17:12:16 +03:00
github.com/openshift/custom-resource-status v1.1.3-0.20220503160415-f2fdb4999d87 // indirect
Bump api, client-go, library-go for k8s 1.31
2024-10-02 13:25:26 -04:00
github.com/openshift/machine-api-operator v0.2.1-0.20240930121047-57b7917e6140 // indirect
power vs installconfig assets: vendoring a seperate commit for the vendor updates Signed-off-by: Christy Norman <christy@linux.vnet.ibm.com>
2022-03-03 12:33:15 -06:00
github.com/opentracing/opentracing-go v1.2.0 // indirect
Import machine-api-provider-gcp util package.
2023-12-18 11:00:55 +01:00
github.com/peterbourgon/diskv v2.0.1+incompatible // indirect
AGENT-702: Generate minimal ISO for external platform - Renamed `ipxeBaseURL` to more generic `bootArtifactsBaseURL` - Removed unwanted lint - Added integration tests to create minimal ISO for external platform with and without bootArtifactsBaseURL in agent-config.yaml - Fixed existing integration tests to include change of name from `ipxeBaseURL` to more generic `bootArtifactsBaseURL` - Added BootArtifactsBaseUrl and bootArtifactsPath into parent asset AgentArtifacts - AgentArtifacts also depends on AgentConfig asset - Moved common code to generate rootfs.img file into extractRootFS() in AgentArtifacts asset - If the bootArtifactsBaseURL is specified, construct the custom rootfs URL otherwise default to the URL from the RHCOS streams file - For external platform when the bootArtifactsBaseUrl is specified, output the rootfs file alongside the minimal ISO - For all other platforms, continue generating full ISO (no explicit rootfs.img is generated) - Vendor changes after updating github.com/openshift/assisted-image-service dependency - set IMAGE_TYPE_ISO to 'minimal-iso' in create-cluster-and-infraenv.service.template when using external platform - Log an info message to upload CCM manifests Signed-off-by: Pawan Pinjarkar <ppinjark@redhat.com>
2023-08-28 12:19:42 -04:00
github.com/pierrec/lz4/v4 v4.1.17 // indirect
azure: Update capz version Updating capz version from v1.11.0 to v1.14.2
2024-04-15 10:23:58 -04:00
github.com/pkg/browser v0.0.0-20240102092130-5ac0b6a4141c // indirect
Update assisted-image-service
2023-07-04 15:43:48 +12:00
github.com/pkg/xattr v0.4.9 // indirect
provision CAPI/CAPV controller
2024-01-30 09:50:36 -05:00
github.com/pmezard/go-difflib v1.0.1-0.20181226105442-5d4384ee4fb2 // indirect
Update cluster-api-provide-azure to v1.21.1
2025-11-03 14:32:44 -05:00
github.com/prometheus/client_model v0.6.2 // indirect
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/prometheus/procfs v0.17.0 // indirect
Import machine-api-provider-gcp util package.
2023-12-18 11:00:55 +01:00
github.com/russross/blackfriday/v2 v2.1.0 // indirect
Update openshift/api Use a version of the OpenShift API that includes the Azure Confidential VM and TrusteLaunch for VMs configuration options. Signed-off-by: Michail Resvanis <mresvani@redhat.com>
2023-07-14 10:36:08 +02:00
github.com/shurcooL/httpfs v0.0.0-20190707220628-8d4bc4ba7749 // indirect
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
github.com/spf13/pflag v1.0.10 // indirect
OCPBUGS-34037: bump github.com/container/images for CVE fix
2024-06-10 18:35:14 +02:00
github.com/syndtr/gocapability v0.0.0-20200815063812-42c35b437635 // indirect
Bump api, client-go, library-go for k8s 1.31
2024-10-02 13:25:26 -04:00
github.com/x448/float16 v0.8.4 // indirect
Import machine-api-provider-gcp util package.
2023-12-18 11:00:55 +01:00
github.com/xlab/treeprint v1.2.0 // indirect
azure: update mod and vendor
2022-11-22 23:22:45 +01:00
github.com/yosida95/uritemplate/v3 v3.0.2 // indirect
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
go.mongodb.org/mongo-driver v1.17.3 // indirect
go.mod: Bump CAPZ and ASO Bumps CAPZ to v1.19.3 and ASO to v2.11.0. Updates go.mod requires and go mod tidy for top-level go.mod, cluster-api/providers/azure(aso).
2025-05-12 10:14:48 -04:00
go.opentelemetry.io/auto/sdk v1.1.0 // indirect
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc v0.61.0 // indirect
go.mod: pull in new stream metadata & arm compute packages go get github.com/coreos/stream-metadata-go@main
2025-08-18 16:15:39 -04:00
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.61.0 // indirect
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
go.opentelemetry.io/otel v1.38.0 // indirect
go.opentelemetry.io/otel/metric v1.38.0 // indirect
go.opentelemetry.io/otel/trace v1.38.0 // indirect
go: update modules Signed-off-by: Vince Prignano <vincepri@redhat.com>
2023-10-31 08:01:50 -07:00
go.uber.org/multierr v1.11.0 // indirect
PowerVS: Vendoring go.* changes Update the installer to use commit c6bcd313bce0fc9866e41bb9e3487d9f61c628a3 of cluster-api-provider-ibmcloud This includes a couple of necessary Transit Gateway fixes.
2024-09-13 10:21:30 -05:00
go.uber.org/zap v1.27.0 // indirect
Update cluster-api-provide-azure to v1.21.1
2025-11-03 14:32:44 -05:00
golang.org/x/exp v0.0.0-20250305212735-054e65f0b394 // indirect
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
golang.org/x/mod v0.29.0
golang.org/x/net v0.46.0 // indirect
golang.org/x/time v0.13.0 // indirect
golang.org/x/tools v0.37.0 // indirect
Upgrading cluster-api-provider-nutanix version to 1.7.0
2025-08-06 12:00:42 +05:30
gomodules.xyz/jsonpatch/v2 v2.5.0 // indirect
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
google.golang.org/genproto v0.0.0-20250603155806-513f23925822 // indirect
google.golang.org/genproto/googleapis/rpc v0.0.0-20251002232023-7c0ddcbb5797 // indirect
google.golang.org/protobuf v1.36.10 // indirect
AGENT-702: Generate minimal ISO for external platform - Renamed `ipxeBaseURL` to more generic `bootArtifactsBaseURL` - Removed unwanted lint - Added integration tests to create minimal ISO for external platform with and without bootArtifactsBaseURL in agent-config.yaml - Fixed existing integration tests to include change of name from `ipxeBaseURL` to more generic `bootArtifactsBaseURL` - Added BootArtifactsBaseUrl and bootArtifactsPath into parent asset AgentArtifacts - AgentArtifacts also depends on AgentConfig asset - Moved common code to generate rootfs.img file into extractRootFS() in AgentArtifacts asset - If the bootArtifactsBaseURL is specified, construct the custom rootfs URL otherwise default to the URL from the RHCOS streams file - For external platform when the bootArtifactsBaseUrl is specified, output the rootfs file alongside the minimal ISO - For all other platforms, continue generating full ISO (no explicit rootfs.img is generated) - Vendor changes after updating github.com/openshift/assisted-image-service dependency - set IMAGE_TYPE_ISO to 'minimal-iso' in create-cluster-and-infraenv.service.template when using external platform - Log an info message to upload CCM manifests Signed-off-by: Pawan Pinjarkar <ppinjark@redhat.com>
2023-08-28 12:19:42 -04:00
gopkg.in/djherbis/times.v1 v1.3.0 // indirect
bump installer capv
2024-09-04 08:17:08 -04:00
gopkg.in/evanphx/json-patch.v4 v4.12.0 // indirect
add go-yaml dependency required to (un)marshall vSphere cloud provider structs properly implements https://github.com/openshift/enhancements/pull/918
2022-06-03 11:10:07 -04:00
gopkg.in/gcfg.v1 v1.2.3 // indirect
refactor: replace `github.com/ghodss/yaml` with `sigs.k8s.io/yaml` At the time of making this commit, the package `github.com/ghodss/yaml` is no longer actively maintained. `sigs.k8s.io/yaml` is a permanent fork of `ghodss/yaml` and is actively maintained by Kubernetes SIG. Signed-off-by: Eng Zer Jun <engzerjun@gmail.com>
2023-03-05 16:13:33 +08:00
gopkg.in/inf.v0 v0.9.1 // indirect
add go-yaml dependency required to (un)marshall vSphere cloud provider structs properly implements https://github.com/openshift/enhancements/pull/918
2022-06-03 11:10:07 -04:00
gopkg.in/warnings.v0 v0.1.2 // indirect
refactor: replace `github.com/ghodss/yaml` with `sigs.k8s.io/yaml` At the time of making this commit, the package `github.com/ghodss/yaml` is no longer actively maintained. `sigs.k8s.io/yaml` is a permanent fork of `ghodss/yaml` and is actively maintained by Kubernetes SIG. Signed-off-by: Eng Zer Jun <engzerjun@gmail.com>
2023-03-05 16:13:33 +08:00
gopkg.in/yaml.v3 v3.0.1 // indirect
Update to latest assisted-service With the assisted-service client now in a separate go module, we are able to drop the dependency on the main assisted-service module. This allows us to update to the latest version without pulling in any undesirable dependencies as a side-effect.
2023-08-22 22:17:27 +12:00
gorm.io/gorm v1.24.5 // indirect
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
k8s.io/apiserver v0.34.1 // indirect
k8s.io/cli-runtime v0.33.4 // indirect
k8s.io/cluster-bootstrap v0.33.3 // indirect
k8s.io/component-base v0.34.1 // indirect
k8s.io/kube-openapi v0.0.0-20250710124328-f3f2b991d03b // indirect
k8s.io/kubectl v0.33.4 // indirect
sigs.k8s.io/kustomize/api v0.19.0 // indirect
sigs.k8s.io/kustomize/kyaml v0.19.0 // indirect
bump(ocp/api): pull in updated DualReplica bumped ocp api to pull in DualReplica being promoted to TechPreview needed to pin apimachinery to kube 32 since bumping to kube 33 caused a dependency on cluster-api 1.11 which is currently in beta Signed-off-by: ehila <ehila@redhat.com>
2025-07-28 11:55:14 -04:00
sigs.k8s.io/randfill v1.0.0 // indirect
Revendor with golang 1.17
2021-11-24 00:43:52 -05:00
)
vendor: update to remove terraform and providers * Replace terraform modules with github.com/hashicorp/terraform-exec. * Remove all terraform providers. * Remove all unneeded replaces. * Tidy up the replace stanzas so that it is more clear why each replace is needed. * Remove and re-create all indirect requires to clean up ones that are no longer needed.
2021-12-22 10:36:51 -05:00
// OpenShift Forks
Add go.mod
2020-02-14 00:00:06 +01:00
replace (
METAL-803: Update vendoring for baremetal-operator Required for RAID config Removes local_gb from terraform properties as its not required and no longer part of the BMO api. Sets to cpu_arch to x86_64 as this is all that is supported by the installer(and its no longer part of the BMO api).
2023-12-07 09:17:16 +00:00
github.com/metal3-io/baremetal-operator => github.com/openshift/baremetal-operator v0.0.0-20231128154154-6736c9b9c6c8
github.com/metal3-io/baremetal-operator/apis => github.com/openshift/baremetal-operator/apis v0.0.0-20231128154154-6736c9b9c6c8
github.com/metal3-io/baremetal-operator/pkg/hardwareutils => github.com/openshift/baremetal-operator/pkg/hardwareutils v0.0.0-20231128154154-6736c9b9c6c8
vendor
2024-08-21 16:26:53 -04:00
k8s.io/cloud-provider-vsphere => github.com/openshift/cloud-provider-vsphere v1.19.1-0.20240626105621-6464d0bb4928
Add go.mod
2020-02-14 00:00:06 +01:00
)
Go modules
2020-10-19 11:20:18 +03:00
OCPBUGS-60538: Update assisted-service dependencies Update to the latest sub-modules of the assisted-service repo. This removes a dependency loop and restores the intended status that the top-level module is not (indirectly) imported.
2025-09-24 15:46:34 +12:00
replace github.com/openshift/assisted-service/api => github.com/openshift/assisted-service/api v0.0.0-20250922204150-a52b83145bea
Update assisted-service vendoring Update to the assisted-service at commit a40422bdea617f16cbdb724d53619ca74773be45. This repo now contains multiple go modules, so we have to add overrides for the internal references to the api and models modules.
2022-09-28 17:04:01 -04:00
OCPBUGS-60538: Update assisted-service dependencies Update to the latest sub-modules of the assisted-service repo. This removes a dependency loop and restores the intended status that the top-level module is not (indirectly) imported.
2025-09-24 15:46:34 +12:00
replace github.com/openshift/assisted-service/client => github.com/openshift/assisted-service/client v0.0.0-20250922204150-a52b83145bea
Update to latest assisted-service With the assisted-service client now in a separate go module, we are able to drop the dependency on the main assisted-service module. This allows us to update to the latest version without pulling in any undesirable dependencies as a side-effect.
2023-08-22 22:17:27 +12:00
OCPBUGS-60538: Update assisted-service dependencies Update to the latest sub-modules of the assisted-service repo. This removes a dependency loop and restores the intended status that the top-level module is not (indirectly) imported.
2025-09-24 15:46:34 +12:00
replace github.com/openshift/assisted-service/models => github.com/openshift/assisted-service/models v0.0.0-20250922204150-a52b83145bea
OCPBUGSM-43189: go.mod: update golang.org/x/crypto Needed to address a broken cryptographic algorithm flaw found in golang.org/x/crypto/ssh.
2022-09-21 17:24:48 +02:00
OCPBUGS-8119: CVE-2023-25173: bump containerd A bug was found in containerd prior to versions 1.6.18 and 1.5.18 where supplementary groups are not set up properly inside a container.
2023-03-08 14:33:53 +01:00
// https://issues.redhat.com/browse/OCPBUGS-8119
OCPBUGS-27507: bump containerd for vulnerability fix
2024-01-23 18:03:12 +01:00
// https://issues.redhat.com/browse/OCPBUGS-27507
replace github.com/containerd/containerd => github.com/containerd/containerd v1.6.26
bump installer capv
2024-09-04 08:17:08 -04:00
replace github.com/vmware-tanzu/vm-operator/pkg/constants/testlabels => github.com/vmware-tanzu/vm-operator/pkg/constants/testlabels v0.0.0-20240404200847-de75746a9505
Vendor updates
2025-02-05 13:25:45 -05:00
// This is to force capi back for the older provider version
replace sigs.k8s.io/controller-runtime => sigs.k8s.io/controller-runtime v0.19.3
bump(ocp/api): pull in updated DualReplica bumped ocp api to pull in DualReplica being promoted to TechPreview needed to pin apimachinery to kube 32 since bumping to kube 33 caused a dependency on cluster-api 1.11 which is currently in beta Signed-off-by: ehila <ehila@redhat.com>
2025-07-28 11:55:14 -04:00
go.mod: bump openshift/api to latest && cluster-api to v1.11 This bumps openshift/api to latest and bumps cluster-api to v1.11. CAPI v1.11 contains breaking changes and not all providers have completed migrating to v1.11 yet. Unfortunately this breaks us and makes it so we are unable to update openshift/api (due to conflicts with the latest apimachinery package which is incompatible with older versions of CAPI). Therefore, I am vendoring in the work-in-progress changes in CAPA, CAPZ, & CAPX. The installer only uses this code to generate the manifests (the controllers are vendored separately), so the risk here is relatively low. This is meant as a temporary measure to unblock us from making progress. Once these providers have completed the merge to v1.11, we should be fine to remove these replaces and vendor as usual.
2025-11-07 09:20:56 -05:00
// Temporary vendoring of upstream providers while they work to update to capi v1.11, which contains breaking changes
// See: https://issues.redhat.com/browse/CORS-4262
replace (
github.com/nutanix-cloud-native/cluster-api-provider-nutanix => github.com/nutanix-cloud-native/cluster-api-provider-nutanix v1.7.2-0.20251007022949-442bc2ebe286
sigs.k8s.io/cluster-api-provider-aws/v2 => github.com/clebs/cluster-api-provider-aws/v2 v2.0.0-20251107144358-6be716cd866c
sigs.k8s.io/cluster-api-provider-azure => github.com/mboersma/cluster-api-provider-azure v0.3.1-0.20251030205607-3161b9cc8d3e
)
Copy Permalink