Skip to content

Go API to create HostRule CRD without TLS fails #1445

Open
@andrew-su

Description

@andrew-su

Describe the bug

When creating a HostRule resource by consuming AKO as a Go library, the TLS field is required. However the CRD identifies it as optional.

Reproduction steps

  1. Create a HostRule resource which does not explicitly define a TLS section:
desired := &aviv1beta1.HostRule{
	ObjectMeta: metav1.ObjectMeta{
		Name: "app1",
		Labels: map[string]string{
			"app": "gslb",
		},
	},
	Spec: aviv1beta1.HostRuleSpec{
		VirtualHost: aviv1beta1.HostRuleVirtualHost{
			FqdnType:          aviv1beta1.Exact,
			Fqdn:              "app.default.example.com",
			EnableVirtualHost: ptr.To(true),
			Gslb: aviv1beta1.HostRuleGSLB{
				Fqdn: "app.example.com",
			},
		},
	},
}
  1. Apply it using the Go client:
_, err := akoclient.AkoV1beta1().HostRules("my-namespace").Create(ctx, desired, metav1.CreateOptions{})
  1. Client reports that TLS Certificate name can not be empty string.

Expected behavior

The resource is applied successfully.

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions