Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for listen (0.19 sec)

  1. cni/README.md

            - If so, calls `istio-iptables` with params to setup pod netns
            - If ambient, sets up the ambient logic.
    
    - `istio-iptables`
        - sets up iptables to redirect a list of ports to the port envoy will listen
        - shared code with istio-init container
        - it will generate an iptables-save config, based on annotations/labels and other settings, and apply it.
    
    ### CmdAdd Sidecar Workflow
    
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Fri May 03 19:29:42 GMT 2024
    - 12.3K bytes
    - Viewed (0)
  2. README.md

    MinIO strongly recommends *against* using compiled-from-source MinIO servers for production environments.
    
    ## Deployment Recommendations
    
    ### Allow port access for Firewalls
    
    By default MinIO uses the port 9000 to listen for incoming connections. If your platform blocks the port by default, you may need to enable access to the port.
    
    ### ufw
    
    Plain Text
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Wed Feb 14 17:51:34 GMT 2024
    - 18.7K bytes
    - Viewed (0)
  3. docs/bucket/notifications/README.md

    ```
    
    Here we see that MinIO performed `HSET` on `minio_events` key.
    
    In case, `access` format was used, then `minio_events` would be a list, and the MinIO server would have performed an `RPUSH` to append to the list. A consumer of this list would ideally use `BLPOP` to remove list items from the left-end of the list.
    
    ## Publish MinIO events via NATS
    
    Install NATS from [here](http://nats.io/).
    
    ### Step 1: Add NATS endpoint to MinIO
    
    Plain Text
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Thu Jan 18 07:03:17 GMT 2024
    - 84K bytes
    - Viewed (2)
Back to top