Uploaded image for project: 'Maistra'
  1. Maistra
  2. MAISTRA-2310 Create CRD for joining meshes into a federated mesh
  3. MAISTRA-2293

Create CRD for joining meshes into a federated mesh

    XMLWordPrintable

Details

    • Sub-task
    • Resolution: Done
    • Major
    • maistra-2.1.0
    • None
    • None
    • None
    • Sprint 3, Sprint 4, Sprint 5, Sprint 6, Sprint 7

    Description

      Define a MeshFederation CRD resource which supports the configuration of:

      • discovery endpoint - the endpoint of the remote mesh
      • trustDomain - the domain used in client certificates (spiffe domain)
      • client ID - the ID of the client allowed to access the local discovery server
      • initial certificate chain - used to validate certificates in the config

      Attachments

        Issue Links

          incorporates

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MAISTRA-2237 Federation Service Discovery traffic encryption

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          is related to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OSSM-2484 Resolve DNS for NetworkGateways retrieved through Federation Service Discovery

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Backlog

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MAISTRA-2242 Support different root certificates

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MAISTRA-2304 Allow MeshFederation resources to be created in other mesh namespaces

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. MAISTRA-2297 Add support for updating MeshFederation resources

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. MAISTRA-2298 Consider writing the discovery service entry directly into the service registry

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. MAISTRA-2299 Improve how users configure federation gateways

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. MAISTRA-2300 Consider alternatives to federation.maistra.io/proxy label on gateways

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          mentioned on

          GitLab Merge request - Updated 2 upstream sources

          GitLab Merge request - Updated 2 upstream sources

          GitLab Merge request - Updated 2 upstream sources

          GitLab Merge request - Updated US source to: 88d11df [authz] MAISTRA-224: Support for authz regex matching on request headers (#236) (#544) (#712)

          GitLab Merge request - Updated US source to: ba9d7c3 OSSM-2369: [federation] Introduces federation deployment (#585) (#699)

          GitLab Merge request - Updated US source to: ba9d7c3 OSSM-2369: [federation] Introduces federation deployment (#585) (#699)

          Activity

            People

              rcernich1 Rob Cernich
              rcernich1 Rob Cernich
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: