Eventing TLS: Update Addressable and AddressStatus

[pierDipi]

As the Eventing TLS feature track describes we should update Addressable and AddressStatus types as follow:

// Addressable provides a generic mechanism for a custom resource
// definition to indicate a destination for message delivery.
//
// Addressable is the schema for the destination information. This is
// typically stored in the object's `status`, as this information may
// be generated by the controller.
type Addressable struct {
	// Name is the name of the address.
	Name *string `json:"name,omitempty"`

	URL *apis.URL `json:"url,omitempty"`

	// Certification Authority (CA) certificates in PEM format
// according to https://www.rfc-editor.org/rfc/rfc7468.
// +optional
	CACerts *string `json:”CACerts,omitempty”`
}

// AddressStatus shows how we expect folks to embed Addressable in
// their Status field.
type AddressStatus struct {
        // …
        // If addresses is present, address will be ignored by clients.
	Address *Addressable `json:"address,omitempty"`

	// List of addresses for different protocols (HTTP and HTTPS)
	// +optional
	Addresses []Addressable `json:addresses,omitempty”`
}

Additional Info

• https://docs.google.com/document/d/1H-x_oji8LqkCyd7tlsSyclmUe7FAmEJPgRxOU_0pkn8/edit?resourcekey=0-lzDIPJsZOP3G17QE_g1lHw#

/good-first-issue
/kind feature
/area API

[knative-prow]

@pierDipi:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

Details

In response to this:

As the Eventing TLS feature track describes we should update Addressable and AddressStatus types as follow:

// Addressable provides a generic mechanism for a custom resource
// definition to indicate a destination for message delivery.
//
// Addressable is the schema for the destination information. This is
// typically stored in the object's `status`, as this information may
// be generated by the controller.
type Addressable struct {
  // Name is the name of the address.
  Name *string `json:"name,omitempty"`

  URL *apis.URL `json:"url,omitempty"`

  // Certification Authority (CA) certificates in PEM format
// according to https://www.rfc-editor.org/rfc/rfc7468.
// +optional
  CACerts *string `json:”CACerts,omitempty”`
}

// AddressStatus shows how we expect folks to embed Addressable in
// their Status field.
type AddressStatus struct {
       // …
       // If addresses is present, address will be ignored by clients.
  Address *Addressable `json:"address,omitempty"`

  // List of addresses for different protocols (HTTP and HTTPS)
  // +optional
  Addresses []Addressable `json:addresses,omitempty”`
}

/kind feature

Additional Info

• https://docs.google.com/document/d/1H-x_oji8LqkCyd7tlsSyclmUe7FAmEJPgRxOU_0pkn8/edit?resourcekey=0-lzDIPJsZOP3G17QE_g1lHw#

/good-first-issue
/kind feature
/area API

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[vishal-chdhry]

/assign