SSL endpoint not responding -> secure.eu-de.bluemix.net - ibm-cloud

According to Bluemix Doc this -> secure.eu-de.bluemix.net -> is the regional endpoint for public Bluemix in Germany - however it seems not to responding.

Related

IBM Cloud: Kubernetes add-on ALB Oauth2 Proxy for App ID integration fails to start

I deployed a containerized app to my IBM Cloud Kubernetes service in a VPC. The app uses App ID for authentication. The deployment pipeline ran successfully. The app seems ready, but when accessing its URL it gives an internal server error (500 status code).
From the Kubernetes dashboard I found that the ALB Oauth Proxy add-on is failing. It is deployed, but does not start.
The deployment seems to fail in the health checks (ping not successful). From the POD logs I found the following as last (and only) entry:
[provider.go:55] Performing OIDC Discovery...
Else, there is not much. Any advise?
Guessing from the missing logs and the failing pings, it seemed related to some network setup. Checking the VPC itself, I found that there was no Public Gateway attached to the subnet. Enabling it allowed outbound traffic. The oauth proxy could contact the App ID instance. The app is working as expected now.
Make sure that the VPC subnets allow outbound traffic and have a Public Gateway enabled.

Is it possible to Public API Gateway -> VPC Link -> NLB -> Private API Gateway?

I have a VPC with multiple private API Gateways. This is so services within the VPC can call other private APIs without leaving VPC.
I have a Public API Gateway that I want my clients to engage with, but I want this Public API Gateway to have it's requests handled by the appropriate private API Gateway.
It doesn't appear that it is trivial to achieve the design I have imagined. Am I missing something? Are there alternate patterns that I should investigate?
I have tried to implement the above design, however the network load balancer requires a target group. It doesn't seem possible to register a target that is a private API Gateway. I have tried to register the VPC Endpoint IPs for the private API gateway, but health checks fail and traffic isn't routed appropriately.
I have also considered using App Mesh to handle this kind of routing, but I do not necessarily want to ship an Envoy proxy layer with each of my lambdas.

Kubernetes Gateway API request chaining

is it possible to chain requests through multiple backends with the new https://gateway-api.sigs.k8s.io/ ?
The idea is to have a flow depending on the response headers of each service ie:
Request -> Gateway -> [ first backend service "Custom forward Header" -> second backend service -> "Custom forward Header" -> x service ] -> Response

How to use 1 external port for 3 applications

I Have a 3 applications,
React Front using NextJs
Spring rest API
WildFly server
But so I only have one external port available, I can use some proxy or gateway to access my applications?
I saw Spring cloud Gateway, could run on my external port and redirecting the request for the correctly app? Or is there a better way?
Like this:
Request ip:8433/app1 -> localhost:9000
Request ip:8433/app2 -> localhost:9001
Request ip:8433/app3 -> localhost:9002
Edit One, Spring cloud Gateway code:
#Bean
public RouteLocator customRouteLocator(RouteLocatorBuilder builder) {
return builder.routes()
.route("API", r -> r.path("/api/**").uri("http://localhost:8084"))
.route("UI", r -> r.path("/ui/**").uri("http://localhost:3000"))
.route("WILDFLY", r -> r.path("/wildfly/**").uri("https://localhost:8087/wildfly"))
.build();
}

Integrating Public Bluemix and Dedicated Bluemix

I'm working on a POC for Blockchain and Bluemix (new to both), and the Dedicated Bluemix doesn't have the Blockchain services in it. So, I moved to the Public Bluemix environment but have to pay for the database usage.
Is there any way we can have a connection between the Public and Dedicated Bluemix environments, such that my application is deployed in Public Bluemix and the database is deployed in the Dedicated Bluemix environment?
It's a technical question...
I can't tell you 100% if this works but you could try this...
From the Public Bluemix create a Secure Gateway connection to a net zone with access to the Dedicated Bluemix, whether that on prem or public dedicated.
On the net zone with access to your Bluemix dedicate you would have to setup a Secure Gateway client, either a Docker image or if you have a Datapower near to your Bluemix dedicated you could use it as your Secure Gateway Client.
Good luck