Please enable JavaScript.

Coggle requires JavaScript to display documents.

VPC (VM (IP addresses (external (from pool, $, static or ephemeral,…

- - - - from subnet IP range
      - subnet DNS can map host name to internal IP
      - static or ephemeral
      - DNS Name
        
        [hostname].[zone].c.[project-id].internal
    - - from pool
      - $
      - static or ephemeral
      - unknown to VM
      - from the Google's range of
        public IP addresses
    - - to assign IP for each service inside VM
        (containers or applications)
        can be taken from primary or secondary IP ranges
  - - - cpu utilizatin
      - monitoring metrics
      - LB capacity
      - queue-based metrics
- - - - 3 Gbps for direct peering
        per tunel
      - must establish 2 VPN tunnels
        (1 in + 1 out from GCP perspective)
      - VPN Clients cannot connect
    - - 99.99 % SLA
      - 2 or 4 tunnels
        (2 out+ 2 in from GCP perspective)
      - 2 external IP addresses
      - must use dynamic routing via BGP
- - - - level 4
      - SSL traffic
      - terminates client SSL
        
        traffic proxy-backend can be SSL or TCP
      - security auto patches
    - - maps URL to backends
      - level 7
      - ports: 80,8080,433
      - ip4, ip6
      - to closest instance group
        
        if has capacity
      - backend service
        
        session affinity (optional)
        
        timeout settings
        
        health check
        
        1..n backends
        
        instance group
        or GCS bucket
        
        balancing mode
        
        cpu utilization
        
        rps
        
        capacity scaler
      - terminates client SSL
        
        need at least on SSL certificate
    - - non SSL
      - terminate clients TCP sessions
        
        traffic proxy-backend can be SSL or TCP
      - level 4
  - - - for internal IP's
      - within region
      - TCP/UDP
      - only IP4
      - has internal IP
      - no PROXY
    - - any level 4 protocol - TCP/UDP/SSL/ICMP
      - any ports
      - no PROXY !
      - forwarding rules:
        
        IP data: host port of the client
      - backend
        
        based on service backed
        
        new way
        
        instance group behind service backend
        
        target pool resource
        
        forwarding rules
        
        old approach
        
        TCP/UDP only
        
        up to 50 pool per project
      - only IP4
      - preserves client IPs
      - within region
    - - proxy based
      - http(s) 1/2
      - Envoy based
  - - - siege -c 250 http://$LB_IP
        
        ab -n 500000 -c 1000 http://$LB_IP/
  - - - VMs
      - GKE clusters