scaleway / crossplane-provider-scaleway Goto Github PK

Hi,

I'm trying to apply an example for scalawag cluster, all the ressources are created but I have this error.

I only encountered this error recently (last tow days)

Maybe the Scaleway crossplane provider is not yet updated to the same level as scaleway-go-sdk
so it generate a private network but in invalid constraint

scaleway-sdk-go: invalid argument(s): private_network_id does not respect constraint, a Private Network is mandatory for this cluster typ

any way to fix it?

@yfodil

The version 0.1.0 does not allow to create new k8s clusters, can we have a release ?

Hello,

The provider version 0.2.0 does not work with the flag --enable-external-secret-stores.

Context:

• Kapsule Kubernetes cluster on Scaleway, or local Kind cluster
• The provider config is set correctly according to the docs at: https://www.scaleway.com/en/docs/tutorials/get-started-crossplane-kubernetes/
• Everything works perfectly with 0.1.0
• Version 0.2.0 cannot run at all
• Crossplane v1.15.0
• Kubernetes 1.25 to 1.29

Steps to reproduce:

• Follow the documentation linked above with the provider at v0.1.0
• Make sure it works and can provision resources on Scaleway
• Change package in Provider to "xpkg.upbound.io/scaleway/provider-scaleway:v0.2.0"
• Apply a ControllerConfig or DeploymentRuntimeConfig on your Provider with the flag

Example with ControllerConfig:

apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  name: provider-scaleway
spec:
  controllerConfigRef:
    name: provider-scaleway
  package: xpkg.upbound.io/scaleway/provider-scaleway:v0.2.0
---
apiVersion: pkg.crossplane.io/v1alpha1
kind: ControllerConfig
metadata:
  name: provider-scaleway
spec:
  args:
  - --enable-external-secret-stores

Example with DeploymentRuntimeConfig:

apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  name: provider-scaleway
spec:
  runtimeConfigRef:
    name: enable-ess
  package: xpkg.upbound.io/scaleway/provider-scaleway:v0.2.0
---
apiVersion: pkg.crossplane.io/v1beta1
kind: DeploymentRuntimeConfig
metadata:
  name: enable-ess
spec:
  deploymentTemplate:
    spec:
      selector: {}
      template:
        spec:
          containers:
            - name: package-runtime
              args:
                - --enable-external-secret-stores

Error Log:

scw-41e9299f4a0b-6c56d96987-zljk5 › package-runtime
{"level":"info","ts":"2024-03-11T16:35:40Z","logger":"provider-scaleway","msg":"Alpha feature enabled","flag":"EnableAlphaExternalSecretStores"}
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x1a6ecb3]
goroutine 1 [running]:
github.com/scaleway/provider-scaleway/internal/controller/account/project.Setup({0x2396258, 0xc000502d00}, {{{0x23879f0, 0xc0002e09f0}, {0x2387390, 0xc0006162e8}, 0x8bb2c97000, 0x1, 0xc00061aa60, 0x0}, ...})
github.com/scaleway/provider-scaleway/internal/controller/account/project/zz_controller.go:32 +0x2f3  github.com/scaleway/provider-scaleway/internal/controller.Setup({0x2396258, 0xc000502d00}, {{{0x23879f0, 0xc0002e09f0}, {0x2387390, 0xc0006162e8}, 0x8bb2c97000, 0x1, 0xc00061aa60, 0x0}, ...})
github.com/scaleway/provider-scaleway/internal/controller/zz_setup.go:159 +0x4d6
main.main()
github.com/scaleway/provider-scaleway/cmd/provider/main.go:124 +0x2128

Workaround:

• Do not use the flag --enable-external-secret-stores
• Use writeConnectionSecretToRef instead of publishConnectionDetailsTo
• Use another tool than Crossplane to patch secret metadata or publish your secrets in external stores

The idea is to automate as much as possible the provider's generation process:

• Detect a new release from the Terraform provider repository with GitHub API and GitHub Actions & update the Terraform provider version in the Makefile of the Crossplane provider
• Check for new resources added in the new release through diffs
• If new resources are found, add them to the Crossplane provider with the help of code generation & boilerplate code

How to get kubeconfig for the created cluster if i created one using crossplane scaleway

Hi all,

we tried to apply the project-resource.
The error was a bit confusing:

apply failed: scaleway-sdk-go: invalid argument(s): organization_id is wrongly formatted, value must be a valid UUID:

But after setting organizationId under forProvider in the creation of the managed-resource worked.

Is there a possibility to set the organization_id in the provider config?
I tried it with organization_id in the secret without success.

Hi,

we are evaluating the crossplane provider right now. Btw we are really happy that scaleway provides one! 🎉

I noticed during tests that the Age under events in a kubectl describe x contains always the value <invalid>.

Events:
  Type    Reason                   Age                            From
                                  Message
  ----    ------                   ----                           ----
                                  -------
  Normal  CreatedExternalResource  <invalid>                      managed/object.scaleway.upbound.io/v1alpha1, kind=bucket  Successfully requested creation of external resource
  Normal  DeletedExternalResource  <invalid> (x9 over <invalid>)  managed/object.scaleway.upbound.io/v1alpha1, kind=bucket  Successfully requested deletion of external resource