I would like to use the Google Container Registry through my own DNS server mapping to my own domain - e.g. registry.mydomain.com. How can I accomplish this mapping?
Related
[Internet Resolver][1]
Hi ,
How can I delete this , it been trying but I am not getting any suitable way to delete it .Thanks
[1]: https://i.stack.imgur.com/5MigP.png
If you are using amazon provided DNS in your VPC then dot (.) rule will be the default for internet resolver pointing to amazon DNS server. You can not delete this as it will be assigned to the default VPC in that AWS account. However you can override that association with your VPC is in question and you can have your custom dot(.) forwarding rule pointing to your own DNS server or another server in the internet such as 8.8.8.8. and have that rules associated with all your VPC to have DNS query resolved accordingly.
However if you are using a custom server make sure you have a system rule in place to resolve amazon owned domain name(amazonaws.com) privately. and associate that system rule with all of your VPCs.
I was trying to deploy docker service using aws app-runner. Deploying a service and running it is very street forward. Once I deployed the app, aws gives me url to access my service. Now I want to route traffic from my domain to this url. In route 53 it doesn't seems this option is not available, I might be wrong. In aws app-runner it self there is an option to link the url generated by aws with my domain name. I follow that option but it seems I have to do dns configuration change and CNAM configuration. Is there anyone who have tried this option and able to guid me? Thanks!
In Google Kubernetes Engine, I created a Load Balancer (External IP Address). I can access it using the IP address. However, I want to get a domain name. ( I am not asking about buying my own domain and adding DNS records ). I am not able to find how to get the url.
For eg. in Azure, in Azure Kubernetes Service, I created a Load Balancer and added a label. So, I can get a url like http://<dns_label_which_i_gave>.<region_name>.cloudapp.azure.com. So, for trial purpose, I don't have to pay for a domain and I can get an easy to read domain name.
How to get the same in GCP Load Balancer?
With Google Cloud you can't do this. The Load balancer expose an IP and you have to create a A record in your registrar to make the link.
I have multiple Service Fabric APIs. Both services are hosted in the same cluster using Kestrel. Currently each service is assigned to a specific port so they show up as
http://service1:123 and
http://service2:456
I would like to access the services using default port 80 for both. Is there a way to do this without having to use Azure API Management?
Sure, Kestrel doesn't support port sharing, but you can:
run on IIS, inside containers.
use the built in reverse proxy
use a (containerized) reverse proxy like Traefik
I want to run an application on Azure service fabric. One service should serve as identity provider. So I installed identity server 4 package on that 'usermanager'. I have also two other services which should use this usermanager for authentication and authorization.
That works on localhost. But on Azure I have the problem that an endpoint must be 'Input' or 'Internal' in my service manifest. But for my usermanager I need both input and internal.
<Endpoint Protocol="http" Name="IdentityServerEndpoint" Type="Input" Port="5000" />
/.well-known/openid-configuration needs 'Internal' and
/connect/authorize?xxxxxx needs 'Input'
I found that for Input endpoints azure service fabric uses the full qualified domain name and for internal endpoints it uses the ip address of the lokal network like 10.0.0.4.
Is there a solution to make an endpoint both input and internal?
Or is there a solution to make identity server 4 to handle two endpoints?
Any ideas to solve this problem?
Believe it or not, the "Type" field in the Endpoint config doesn't actually do anything on any hosting platform. It's just metadata that you can configure and use in your code (basically a way for you to set your own policies). It doesn't matter what you put there otherwise.
Ultimately, you're opening an endpoint on a process on a VM. That endpoint will be open on the VM's IP and the port you choose, e.g., 10.0.0.1:5000.
If you want that endpoint to also be available on your cluster's VIP and FQDN, that configuration is external to Service Fabric. In Azure you just need to configure the Azure Load Balancer to forward external traffic on the port your service is listening on. See here for more info on that: https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-connect-and-communicate-with-services#connections-from-external-clients