mittwald icon

mittwald

Interact with mittwald mStudio API

Actions409

Overview

This node interacts with the Mittwald mStudio API to update TLS settings for a specific ingress within a domain. It is designed to modify the TLS configuration of an ingress resource by sending updated parameters such as whether to use ACME (Automatic Certificate Management Environment) for certificate management.

Common scenarios include automating the renewal or update of TLS certificates for ingresses in a Kubernetes environment managed via Mittwald's platform, or toggling ACME usage programmatically.

Practical example: Automatically updating the TLS settings of an ingress after deploying a new service version, ensuring secure HTTPS communication without manual intervention.

Properties

Name Meaning
Ingress Id The unique identifier of the ingress resource whose TLS settings are to be updated.
Acme Boolean flag indicating whether ACME should be used for automatic certificate management.
Is Created A boolean property that was added mistakenly and does not affect the operation.
Request Deadline A string property that was added mistakenly and does not affect the operation.

Output

The node outputs JSON data representing the response from the Mittwald mStudio API after attempting to update the ingress TLS settings. This typically includes confirmation of the update status or details about the ingress TLS configuration.

No binary data output is involved.

Dependencies

  • Requires an API key credential for authenticating with the Mittwald mStudio API.
  • The node uses the base URL https://api.mittwald.de for all requests.
  • Proper network access to Mittwald's API endpoint is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing ingress ID will cause the API call to fail.
    • Incorrect or expired API credentials will result in authentication errors.
    • Network connectivity problems can prevent successful API communication.
  • Error messages:

    • Authentication failures usually indicate invalid API keys; verify and update credentials.
    • "Ingress not found" errors suggest the provided ingress ID does not exist; double-check the ID.
    • Timeout or connection errors may require checking network settings or retrying later.

Links and References

Discussion