google-compute-engine

Kubernetes pod autoscaling out of sync with Instance Group autoscaling

泪湿孤枕 提交于 2020-01-04 09:27:22
问题 I have a simple wordpress site defined by the ReplicationController and Service below. Once the app is deployed and running happily, I enabled autoscaling on the instance group created by Kubernetes by going to the GCE console and enabling autoscaling with the same settings (max 5, cpu 10). Autoscaling the instances and the pods seem to work decent enough except that they keep going out of sync with each other. The RC autoscaling removes the pods from the CE instances but nothing happens with

Kubernetes pod autoscaling out of sync with Instance Group autoscaling

本小妞迷上赌 提交于 2020-01-04 09:27:21
问题 I have a simple wordpress site defined by the ReplicationController and Service below. Once the app is deployed and running happily, I enabled autoscaling on the instance group created by Kubernetes by going to the GCE console and enabling autoscaling with the same settings (max 5, cpu 10). Autoscaling the instances and the pods seem to work decent enough except that they keep going out of sync with each other. The RC autoscaling removes the pods from the CE instances but nothing happens with

Gitlab - Google compute engine Continuous delivery

走远了吗. 提交于 2020-01-04 02:08:22
问题 What I am trying to do is to enable Continuous delivery from GitLab to my compute engine on Google Cloude. I have Ubuntu 16.04 TSL running over there. I did install all components needed to run my project like: Swift, vapor, nginx. I have manage to install Gitlab runner as well and created a runner whcihc is accessible from my gitlab repo. Everytime I do push on master the runner triggers. What happen is a failure due to: could not create leading directories of '/home/gitlab-runner/builds

GCE - We are unable to connect to the VM on port 22

这一生的挚爱 提交于 2020-01-03 17:04:03
问题 I'm having the following error when I try to connect via SSH to my instance on Google Compute Engine. Connection Failed. We are unable to connect to the VM on port 22. Steps I did to get that error Created a new instance using an Ubuntu template. Connected via SSH and installed all my required apps. Deleted the instance but without deleting the boot disk when instance is deleted. Created a new custom image using the boot disk of the deleted instance. started a new instance using the custom

'EntryPoint' object has no attribute 'resolve' when using Google Compute Engine

▼魔方 西西 提交于 2020-01-03 07:37:09
问题 I have an issue related to Cryptography package in Python. Can you please help in resolving these, if possible ? (tried a lot, but couldnt figure out the exact solution) The python code which initiates this error: print("Salt: %s" % salt) server_key = pyelliptic.ECC(curve="prime256v1") # ----->> Line2 print("Server_key: %s" % server_key) # ----->> Line3 server_key_id = base64.urlsafe_b64encode(server_key.get_pubkey()[1:]) http_ece.keys[server_key_id] = server_key http_ece.labels[server_key_id

How to connect from a pool of Google Compute Engine instances to Cloud SQL DB in the same project?

心已入冬 提交于 2020-01-03 02:55:10
问题 If I have a pool of Compute Engine instances (behind a load-balancer with a static IP), and I want to connect from Java apps on these instances to a Cloud Sql database in the same project, what's the way to about it? 1) These instances in the load balancer don't have static external IPs, so I can't authorize access to Cloud SQL by IP addresses. 2) "com.mysql.jdbc.GoogleDriver" is not available on Compute Engine, as it is on App Engine. 3) If I try to use the stock MySql JDBC driver, it doesn

How to save state when preempted on a Google preemptible instance?

守給你的承諾、 提交于 2020-01-03 01:53:08
问题 I need to be able to save the state of a Centos-based Google Compute instance when it first receives a preemption signal. The documentation very clearly indicates that a "ACPI G2 Soft Off" signal is sent 30 seconds before a preemptible shutdown. Unfortunately, Google has given no examples to demonstrate how to capture this signal and I have not yet found a way to capture it. My initial attempts have all been focused around the ACPI Interface using the acpid daemon. Using it, I have been able

GCP open firewall only to cloud shell

守給你的承諾、 提交于 2020-01-02 11:03:15
问题 Is there a way in GCP to explicitly allow firewall rule only from cloud shell. All the GCP demos and videos add the rule allow 22 to 0.0.0.0/0 to ssh to the instance from cloud shell. However is there a way we could restrict the access only from cloud shell - either using cloud shell's IP range or service account ? 回答1: Google does not publish the public IP address range for Cloud Shell. VPC firewall rules allow specifying the service account of the source and target. However, Cloud Shell

GCP open firewall only to cloud shell

混江龙づ霸主 提交于 2020-01-02 11:02:46
问题 Is there a way in GCP to explicitly allow firewall rule only from cloud shell. All the GCP demos and videos add the rule allow 22 to 0.0.0.0/0 to ssh to the instance from cloud shell. However is there a way we could restrict the access only from cloud shell - either using cloud shell's IP range or service account ? 回答1: Google does not publish the public IP address range for Cloud Shell. VPC firewall rules allow specifying the service account of the source and target. However, Cloud Shell

GCP open firewall only to cloud shell

孤人 提交于 2020-01-02 11:01:19
问题 Is there a way in GCP to explicitly allow firewall rule only from cloud shell. All the GCP demos and videos add the rule allow 22 to 0.0.0.0/0 to ssh to the instance from cloud shell. However is there a way we could restrict the access only from cloud shell - either using cloud shell's IP range or service account ? 回答1: Google does not publish the public IP address range for Cloud Shell. VPC firewall rules allow specifying the service account of the source and target. However, Cloud Shell