v1.2.2

Gateway Configuration

Dynamic Repositories can now be bootstrapped

• Eliminates the need for an apply after the Gateway is ready
  • Limitations
    • singleton configs (scheduledTasks that only run on one node + Outbound JMSDestinations) still need to be applied after the Gateway starts
    • the encryptionPasshprase needs to be the same. We do not perform decryption and reencryption in during init

app:
  repositoryReferenceBootstrap:
    enabled: true
    preferGit: false

Expanded Delete support

• Extended to non-statestore repository types
  • local repositories are not included in this release
  • disabling a repository will trigger a delete
    • a new flag (repositoryReferenceDelete.reconcileReferences) has been introduced to mitigate the risk of dependency overlaps
      • repo1 and 2 contain cwpX ==> repo1 is removed cwpX is removed ==> repo2 is automatically re-applied bringing the gateway back to desired state
• repositoryReference directory changes will trigger delete if resulting bundle removes entities
• delete mappings are automatically generated for new commits where entities are removed.

app:
    repositoryReferenceDelete:
      enabled: false <== disabled by default. The Operator will delete repositories from the Gateway when you disable them. Use with caution! Make sure you understand how your configuration is built.
      reconcileReferences: true <== reconcile other repositories after a delete
      reconcileDirectoryChanges: true <== reconcile changes to directories 
      includeEfs: false <== if you do not have a layer7 statestore this flag will enable use of the operators ephemeral filesystem. Not recommended for database backed gateways, use mappings instead. 

More advanced fallback support

• Multiple sources checked when repositories aren't ready to apply

StateStore references

• statestore reconcile is more conservative to avoid egress charges in Cloud vendors
• new preferGit option for bootstrapping repositories
• statestore repositories do not have any state stored in Kubernetes secrets

Advanced directory support

• git repos can contain nested structures
  • these are detected and can be built and combined individually in order
  • omitting directories builds and combines everything. If there are multiple repository structures there is no determinate structure.
  • if directories change, the delta between previous and new is built and applied
  • http and local repository types do not have advanced directory support in this release

app:
  repositoryReferences:
    - name: combined-repo-v1
       type: dynamic
       enabled: true
       directories:
       - l7GWMyFramework <== ignores nested repos
       - l7GWMyFramework/l7GWMyAPIs <== nested repo
       - l7GWMySubscriptions
       - l7GWMyAPIs

Repository Configuration

• The repository controller has expanded responsibility for building combined bundles.

StateStore Configuration

• Added SSL/TLS Support for Redis

Issues

#90 - Expanded directory support should facilitate defining one repository with one or selected directories in the repositoryReference.
#77 - This is now automatically set if left empty in Openshift.
#78 - This will be addressed in documentation and potentially added to a later release.

layer7-operator-0.1.9

The Layer7 Operator Helm Chart

layer7-operator-0.1.8

The Layer7 Operator Helm Chart

v1.2.1

- updated for operator and portal release

- v1.2.1 operator
- 5.3.3 portal

v1.2.0

Gateway Configuration

Graphman Schema

• Updated to Gateway v11.1.2
  • Introduces one change to AuditConfigurations
  • Does not include the experimental kerberos configuration support
• Examples updated to Gateway v11.1.2

OTK Integration

• Single Mode Ephemeral upgraded from Experimental to Preview
• See examples
  • This comes with an example customizations repository and a guide detailing how to create your own
• OTel SDK Only Configuration
  • New otel configuration section that enables setting OTEL_RESOURCE_ATTRIBUTES

Gateway Status

• Added additional status detail for failed graphman calls

State Stores

• A L7StateStore CRD has been introduced
  • Facilitates an integration with an external state store for repositories
  • Initially targeted at Redis, will be expanded to additional providers in the future
    • reduces dependency on Git for large repositories
    • supports bootstrap
    • supports delete (experimental)

Repositories

• L7StateStore integration added

Resolved Issues

• Azure Devops Repositories fail to sync
  • Related to Upload Pack error
    • #70

spec:
  enabled: true
  endpoint: <endpoint>
  branch: main
  type: git
  auth:
    vendor: azure
    ...

• Graphman
  • Resolved an issue where policyBackedIdps would fail to apply
• Default SSL key loaded from manifest but not active
  • #63
• InstallModes for OperatorHub + Openshift Operator Catalog
  • #62
  • Applied to OperatorHub, requires more work for the Openshift Operator Catalog

layer7-operator-0.1.7

The Layer7 Operator Helm Chart

v1.1.1

Layer7 Operator v1.1.1 Release

Dependency Updates

• Golang 1.22.0 ==> 1.23.3
• Other dependencies

Removals

• Kube RBAC Proxy
  • resolves #60

Updates

• Fixed an issue where external keys would not sync correctly

Testing

• CI Tooling updated
• Kubernetes 1.30 ==> 1.31

layer7-operator-0.1.6

The Layer7 Operator Helm Chart

v1.1.0

Layer7 Operator v1.1.0 Release

Highlights

• Experimental API Developer Portal Integration
  The Operator now supports an experimental integration between the Portal and ephemeral container Gateways with a ground to cloud agent

• Local Repositories
  The Operator now supports local repositories in the form of Graphman bundles stored in Kubernetes secrets requiring zero external dependencies and with faster change detection and synchronization

• Trusted Certificate Support
  The Operator now supports managing gateway trusted certificates externally using Kubernetes secrets

• Gateway Custom Resource Driven Entity Management
  Direct, dynamic, zero restart, full CRUD entity management for the the following entities via Gateway custom resource changes:

  • Cluster Properties
  • Listen Ports
  • External Secrets
  • External Keys
  • External Certs

• Automatic Gateway Restart on Configuration Changes
  The Operator can now optionally restart container Gateways when certain configuration properties that are read on Gateway startup are changed in their Gateway custom resource definition

• Automatic Resource Cleanup
  The Operator will attempt to automatically cleanup associated resources when any of the following Kubernetes configuration options are disabled in a Gateway custom resource:

  • Ingress/Routes
  • PodDisruptionBudgets
  • HorizontalPodAutoscalers

layer7-operator-0.1.5

The Layer7 Operator Helm Chart