Skip to content

Changing GATEKEEPER default running port produces errors #85

Description

@fedjo

In the example.env changing the GK running port is not an easy task as it has to be changed in multiple places.

Moreover, after changing the post to the env file , the healthcheck in the gatekeeper.yml fails to run as it still uses the fedault port.

Solution

Simplify the process of changing the GK running port by using a single variable to define the port, if possible

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions