Duration to provision a new TLS certificate on GCP HTTPS-Load-Balancer?GCP Load Balancer High AvailabilityGCP Load Balancer - Instance Failing - Debug?Is gcp https load-balancer Frontend can listen on port other than 443?GCP Https Load Balancer SSL CertificateXMPP behind a GCP TCP/SSL proxy load balancerHow to accept HTTPS and Websockets on a new Google Kubernetes Engine deployment?Setting up a SSL Certificate IN GCP load balancerLet's Encrypt SSL on Google CloudSlow GCP HTTP Global Load Balancer configuration405 Error - Handling CONNECT requests with GCP Load Balancer
Set multicolumn to a exact width
Has there been any indication at all that further negotiation between the UK and EU is possible?
Can the negators "jamais, rien, personne, plus, ni, aucun" be used in a single sentence?
Is it possible writing coservation of relativistic energy in this naive way?
In the Marvel universe, can a human have a baby with any non-human?
Is it illegal to withhold someone's passport and green card in California?
Employer wants to use my work email account after I quit
How convert text to hex value?
Hot coffee brewing solutions for deep woods camping
What's currently blocking the construction of the wall between Mexico and the US?
Suggested order for Amazon Prime Doctor Who series
How much will studying magic in an academy cost?
Are all instances of trolls turning to stone ultimately references back to Tolkien?
Interaction between Leyline of Anticipation and Teferi, Time Raveler
Is there a maximum distance from a planet that a moon can orbit?
Long term BTC investing
Hand soldering SMD 1206 components
How risky is real estate?
Why is C++ initial allocation so much larger than C's?
What was the Shuttle Carrier Aircraft escape tunnel?
Is a single radon-daughter atom in air a solid?
How would modern naval warfare have to have developed differently for battleships to still be relevant in the 21st century?
Should I prioritize my 401(k) over my student loans?
Why do some games show lights shine thorugh walls?
Duration to provision a new TLS certificate on GCP HTTPS-Load-Balancer?
GCP Load Balancer High AvailabilityGCP Load Balancer - Instance Failing - Debug?Is gcp https load-balancer Frontend can listen on port other than 443?GCP Https Load Balancer SSL CertificateXMPP behind a GCP TCP/SSL proxy load balancerHow to accept HTTPS and Websockets on a new Google Kubernetes Engine deployment?Setting up a SSL Certificate IN GCP load balancerLet's Encrypt SSL on Google CloudSlow GCP HTTP Global Load Balancer configuration405 Error - Handling CONNECT requests with GCP Load Balancer
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
What's the expected duration to provision/finish serving an updated TLS certificate (called "SSL certificate resource" in GCE) for the target HTTPS proxy (part of the GCP HTTPS-Load-Balancer)? Is it documented somewhere?
My test below reveals:
- GCP HTTPS-Load-Balancer needs ca. 8 minutes after updating to serve only the new TLS certificate
- ... ca. 7 minutes after applying to serve only the old certificate
Test setup
18:44 Update the proxy to use the new TLS certificate (keeping the old
certificate_valid-2019-07as "backup")gcloud compute target-https-proxies update NAME --ssl-certificates certificate_valid-2021-07,certificate_valid-2019-07(running each 5 seconds:
gcloud compute target-https-proxies list --filter="name=NAME")&curl -v https://LOAD_BALANCER_IP 2>&1 | grep "expire date")all requests serve certificate with
expire date: 2019-07- 18:44:41 switch to SSL resources
certificate_valid-2021-07,certificate_valid-2019-07 18:50:26 switch back to SSL resource
certificate_valid-2019-07(automatically done byingress-gce)18:52:04 first
expire date: 2021-07appeared- 18:52:35 all requests
expire date: 2021-07 - 18:56:34 first
expire date: 2019-07appeared - 18:57:10 all requests
expire date: 2019-07
load-balancing
google-cloud-platform google-compute-engine ssl-certificate-renewal google-cloud-http-load-balancer asked Jun 6 at 19:03
DominikDominik
1364 bronze badges
add a comment |
What's the expected duration to provision/finish serving an updated TLS certificate (called "SSL certificate resource" in GCE) for the target HTTPS proxy (part of the GCP HTTPS-Load-Balancer)? Is it documented somewhere?
My test below reveals:
- GCP HTTPS-Load-Balancer needs ca. 8 minutes after updating to serve only the new TLS certificate
- ... ca. 7 minutes after applying to serve only the old certificate
Test setup
18:44 Update the proxy to use the new TLS certificate (keeping the old
certificate_valid-2019-07as "backup")gcloud compute target-https-proxies update NAME --ssl-certificates certificate_valid-2021-07,certificate_valid-2019-07(running each 5 seconds:
gcloud compute target-https-proxies list --filter="name=NAME")&curl -v https://LOAD_BALANCER_IP 2>&1 | grep "expire date")all requests serve certificate with
expire date: 2019-07- 18:44:41 switch to SSL resources
certificate_valid-2021-07,certificate_valid-2019-07 18:50:26 switch back to SSL resource
certificate_valid-2019-07(automatically done byingress-gce)18:52:04 first
expire date: 2021-07appeared- 18:52:35 all requests
expire date: 2021-07 - 18:56:34 first
expire date: 2019-07appeared - 18:57:10 all requests
expire date: 2019-07
load-balancing
google-cloud-platform google-compute-engine ssl-certificate-renewal google-cloud-http-load-balancer asked Jun 6 at 19:03
DominikDominik
1364 bronze badges
add a comment |
What's the expected duration to provision/finish serving an updated TLS certificate (called "SSL certificate resource" in GCE) for the target HTTPS proxy (part of the GCP HTTPS-Load-Balancer)? Is it documented somewhere?
My test below reveals:
- GCP HTTPS-Load-Balancer needs ca. 8 minutes after updating to serve only the new TLS certificate
- ... ca. 7 minutes after applying to serve only the old certificate
Test setup
18:44 Update the proxy to use the new TLS certificate (keeping the old
certificate_valid-2019-07as "backup")gcloud compute target-https-proxies update NAME --ssl-certificates certificate_valid-2021-07,certificate_valid-2019-07(running each 5 seconds:
gcloud compute target-https-proxies list --filter="name=NAME")&curl -v https://LOAD_BALANCER_IP 2>&1 | grep "expire date")all requests serve certificate with
expire date: 2019-07- 18:44:41 switch to SSL resources
certificate_valid-2021-07,certificate_valid-2019-07 18:50:26 switch back to SSL resource
certificate_valid-2019-07(automatically done byingress-gce)18:52:04 first
expire date: 2021-07appeared- 18:52:35 all requests
expire date: 2021-07 - 18:56:34 first
expire date: 2019-07appeared - 18:57:10 all requests
expire date: 2019-07
load-balancing
google-cloud-platform google-compute-engine ssl-certificate-renewal google-cloud-http-load-balancer asked Jun 6 at 19:03
DominikDominik
1364 bronze badges
What's the expected duration to provision/finish serving an updated TLS certificate (called "SSL certificate resource" in GCE) for the target HTTPS proxy (part of the GCP HTTPS-Load-Balancer)? Is it documented somewhere?
My test below reveals:
- GCP HTTPS-Load-Balancer needs ca. 8 minutes after updating to serve only the new TLS certificate
- ... ca. 7 minutes after applying to serve only the old certificate
Test setup
18:44 Update the proxy to use the new TLS certificate (keeping the old
certificate_valid-2019-07as "backup")gcloud compute target-https-proxies update NAME --ssl-certificates certificate_valid-2021-07,certificate_valid-2019-07(running each 5 seconds:
gcloud compute target-https-proxies list --filter="name=NAME")&curl -v https://LOAD_BALANCER_IP 2>&1 | grep "expire date")all requests serve certificate with
expire date: 2019-07- 18:44:41 switch to SSL resources
certificate_valid-2021-07,certificate_valid-2019-07 18:50:26 switch back to SSL resource
certificate_valid-2019-07(automatically done byingress-gce)18:52:04 first
expire date: 2021-07appeared- 18:52:35 all requests
expire date: 2021-07 - 18:56:34 first
expire date: 2019-07appeared - 18:57:10 all requests
expire date: 2019-07
load-balancing
google-cloud-platform google-compute-engine ssl-certificate-renewal google-cloud-http-load-balancer load-balancing
google-cloud-platform google-compute-engine ssl-certificate-renewal google-cloud-http-load-balancer asked Jun 6 at 19:03
DominikDominik
1364 bronze badges
asked Jun 6 at 19:03
DominikDominik
1364 bronze badges
edited Jun 6 at 19:27
Dominik
asked Jun 6 at 19:03
DominikDominik
1364 bronze badges
asked Jun 6 at 19:03
DominikDominik
1364 bronze badges
asked Jun 6 at 19:03
DominikDominik
1364 bronze badges
1364 bronze badges
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I don't see any documentation specifying exactly what you want to know. The only related information I can find is this.
answered Jun 7 at 7:57
Alex6ZamAlex6Zam
112 bronze badges
The doc you linked is about provisioning a new TLS/SSL certificate itself. My question is about the time to provision an already existing certificate to the global load-balancer instances. I guess the duration will be the same for the managed certificate once it's successfully created.
– Dominik
Jun 7 at 12:26
You are right, the documentation is about provisioning new certificates and that's the most close documentation I found. Regarding your question we can only speculate or made your own measurements, as you already did. In the field of the speculation, I agree with you in that must take a similar among of time than used for managed certificates once its are created.
– Alex6Zam
Jun 7 at 13:17
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f970438%2fduration-to-provision-a-new-tls-certificate-on-gcp-https-load-balancer%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I don't see any documentation specifying exactly what you want to know. The only related information I can find is this.
answered Jun 7 at 7:57
Alex6ZamAlex6Zam
112 bronze badges
The doc you linked is about provisioning a new TLS/SSL certificate itself. My question is about the time to provision an already existing certificate to the global load-balancer instances. I guess the duration will be the same for the managed certificate once it's successfully created.
– Dominik
Jun 7 at 12:26
You are right, the documentation is about provisioning new certificates and that's the most close documentation I found. Regarding your question we can only speculate or made your own measurements, as you already did. In the field of the speculation, I agree with you in that must take a similar among of time than used for managed certificates once its are created.
– Alex6Zam
Jun 7 at 13:17
add a comment |
I don't see any documentation specifying exactly what you want to know. The only related information I can find is this.
answered Jun 7 at 7:57
Alex6ZamAlex6Zam
112 bronze badges
The doc you linked is about provisioning a new TLS/SSL certificate itself. My question is about the time to provision an already existing certificate to the global load-balancer instances. I guess the duration will be the same for the managed certificate once it's successfully created.
– Dominik
Jun 7 at 12:26
You are right, the documentation is about provisioning new certificates and that's the most close documentation I found. Regarding your question we can only speculate or made your own measurements, as you already did. In the field of the speculation, I agree with you in that must take a similar among of time than used for managed certificates once its are created.
– Alex6Zam
Jun 7 at 13:17
add a comment |
I don't see any documentation specifying exactly what you want to know. The only related information I can find is this.
answered Jun 7 at 7:57
Alex6ZamAlex6Zam
112 bronze badges
I don't see any documentation specifying exactly what you want to know. The only related information I can find is this.
answered Jun 7 at 7:57
Alex6ZamAlex6Zam
112 bronze badges
answered Jun 7 at 7:57
Alex6ZamAlex6Zam
112 bronze badges
answered Jun 7 at 7:57
Alex6ZamAlex6Zam
112 bronze badges
answered Jun 7 at 7:57
Alex6ZamAlex6Zam
112 bronze badges
112 bronze badges
The doc you linked is about provisioning a new TLS/SSL certificate itself. My question is about the time to provision an already existing certificate to the global load-balancer instances. I guess the duration will be the same for the managed certificate once it's successfully created.
– Dominik
Jun 7 at 12:26
You are right, the documentation is about provisioning new certificates and that's the most close documentation I found. Regarding your question we can only speculate or made your own measurements, as you already did. In the field of the speculation, I agree with you in that must take a similar among of time than used for managed certificates once its are created.
– Alex6Zam
Jun 7 at 13:17
add a comment |
The doc you linked is about provisioning a new TLS/SSL certificate itself. My question is about the time to provision an already existing certificate to the global load-balancer instances. I guess the duration will be the same for the managed certificate once it's successfully created.
– Dominik
Jun 7 at 12:26
You are right, the documentation is about provisioning new certificates and that's the most close documentation I found. Regarding your question we can only speculate or made your own measurements, as you already did. In the field of the speculation, I agree with you in that must take a similar among of time than used for managed certificates once its are created.
– Alex6Zam
Jun 7 at 13:17
The doc you linked is about provisioning a new TLS/SSL certificate itself. My question is about the time to provision an already existing certificate to the global load-balancer instances. I guess the duration will be the same for the managed certificate once it's successfully created.
– Dominik
Jun 7 at 12:26
The doc you linked is about provisioning a new TLS/SSL certificate itself. My question is about the time to provision an already existing certificate to the global load-balancer instances. I guess the duration will be the same for the managed certificate once it's successfully created.
– Dominik
Jun 7 at 12:26
You are right, the documentation is about provisioning new certificates and that's the most close documentation I found. Regarding your question we can only speculate or made your own measurements, as you already did. In the field of the speculation, I agree with you in that must take a similar among of time than used for managed certificates once its are created.
– Alex6Zam
Jun 7 at 13:17
You are right, the documentation is about provisioning new certificates and that's the most close documentation I found. Regarding your question we can only speculate or made your own measurements, as you already did. In the field of the speculation, I agree with you in that must take a similar among of time than used for managed certificates once its are created.
– Alex6Zam
Jun 7 at 13:17
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f970438%2fduration-to-provision-a-new-tls-certificate-on-gcp-https-load-balancer%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
