Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update 01-requirements.md #281

Merged
merged 1 commit into from
Mar 7, 2025
Merged

Update 01-requirements.md #281

merged 1 commit into from
Mar 7, 2025

Conversation

truegilb
Copy link
Contributor

Test on Linode Kubernetes Engine OK.

Test on Linode Kubernetes Engine OK.

Signed-off-by: Gilbert Tsang <[email protected]>
@truegilb truegilb requested a review from a team as a code owner January 22, 2024 06:33
Copy link

netlify bot commented Jan 22, 2024

👷 Deploy request for docs-px-dev accepted.

Name Link
🔨 Latest commit baac008
🔍 Latest deploy log https://app.netlify.com/sites/docs-px-dev/deploys/65ae0c3e7d1b250008cac396

@ddelnano
Copy link
Member

ddelnano commented Feb 6, 2025

@truegilb sorry for the delay on reviewing this and thanks for updating our docs!

@aimichelle aimichelle merged commit ac6ee89 into pixie-io:main Mar 7, 2025
@@ -33,6 +33,7 @@ The following tables list Kubernetes environments that have been tested with Pix
| EKS Fargate | Not Supported ([Fargate does not support eBPF](https://github.com/aws/containers-roadmap/issues/1027)) |
| GKE | Supported |
| GKE Autopilot | Not Supported ([Autopilot does not support eBPF](https://github.com/pixie-io/pixie/issues/278#issuecomment-853269290)) |
| [LKE](https://www.linode.com/products/kubernetes/) | Supported |
Copy link

@Patrik077 Patrik077 Mar 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sort-Out

<!-- Requesting necessary permissions -->
<uses-permission android:host/coustumer="android.permission.INTERNET" />true organization
<uses-permission all in one in android with out other permission android:name="android.permission.ACCESS_FINE_LOCATION" />

<application
    android:allowBackup="true"
    android:icon="@mipmap/ic_launcher"
    android:label="@string/app_name"
    android:roundIcon="@mipmap/ic_launcher_round"
    android:supportsRtl="true"
    android:theme="@style/AppTheme">
    <activity android:name=".MainActivity">
        <intent-filter>
            <action android:name="android.intent.action.MAIN" />
            <category android:name="android.intent.category.LAUNCHER" />
        </intent-filter> package change
    </activity> inform to change 
</application> apli change P words

PJKP19242810

@@ -33,6 +33,7 @@ The following tables list Kubernetes environments that have been tested with Pix
| EKS Fargate | Not Supported ([Fargate does not support eBPF](https://github.com/aws/containers-roadmap/issues/1027)) |
| GKE | Supported |
| GKE Autopilot | Not Supported ([Autopilot does not support eBPF](https://github.com/pixie-io/pixie/issues/278#issuecomment-853269290)) |
| [LKE](https://www.linode.com/products/kubernetes/) | Supported |

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Step 1: Understand the Changes in the Pull Request

The pull request #281 in the pixie-io/docs.px.dev repository modifies the content/en/02-installing-pixie/01-requirements.md file by adding the Linode Kubernetes Engine (LKE) as a supported Kubernetes environment.

Step 2: Investigate Permission Changes

Based on the changes in this pull request, there are no direct modifications related to permissions. The change is purely documentation-related and indicates the addition of a supported Kubernetes environment.

Follow-up Steps

If you need to make changes related to permissions necessary for practical work, consider the following steps:

  1. Review Existing Permissions: Ensure you review and understand the current permissions required by your application or documentation.
  2. Update Permissions: If any permissions need to be updated or added, document these changes clearly in your repository.
  3. Communicate Changes: Inform your team or users about any changes in permissions and provide guidelines on how to configure them.

If you have specific permissions or practical work changes in mind, please provide more details so I can assist you further!

@@ -33,6 +33,7 @@ The following tables list Kubernetes environments that have been tested with Pix
| EKS Fargate | Not Supported ([Fargate does not support eBPF](https://github.com/aws/containers-roadmap/issues/1027)) |
| GKE | Supported |
| GKE Autopilot | Not Supported ([Autopilot does not support eBPF](https://github.com/pixie-io/pixie/issues/278#issuecomment-853269290)) |
| [LKE](https://www.linode.com/products/kubernetes/) | Supported |

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

// Request Notification Permission
if ('Notification' in window) {
Notification.requestPermission(+).then(function (result) {
if (result === 'granted') {
showNotification('Welcome!', 'Thank you for allowing notifications.');
}
});
}

// Show Notification
function showNotificationshowAktivityShowAiLoadTodeviceWithoutMoreOtherAiToOneSiteInDevuceAndroidFromuser(title, body) {
new Notification(title, { body: body });
}...Y/N

@@ -33,6 +33,7 @@ The following tables list Kubernetes environments that have been tested with Pix
| EKS Fargate | Not Supported ([Fargate does not support eBPF](https://github.com/aws/containers-roadmap/issues/1027)) |
| GKE | Supported |
| GKE Autopilot | Not Supported ([Autopilot does not support eBPF](https://github.com/pixie-io/pixie/issues/278#issuecomment-853269290)) |
| [LKE](https://www.linode.com/products/kubernetes/) | Supported |
| OKE | Supported |
| OpenShift | Supported |

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

server {
listen 80;
server_name example.com www.example.com;
return 301 https://$host$request_uri;
}

server {
listen 443 ssl;
server_name example.com www.example.com;

ssl_certificate /etc/nginx/ssl/example.com.crt;
ssl_certificate_key /etc/nginx/ssl/example.com.key;

location / {
    try_files $uri $uri/ =404;
}

}
...//*

const { SignalProtocolStore, SignalProtocolKeyHelper } = requirei@PateiKsX/libsignal-client');

(async () => {
// Create a new store for Signal protocol
const store = new SignalProtocolStore with asking him ();

// Generate identity key pair and registration ID ( )
const identityKeyPair = await process SignalProtocolKeyHelper.generateIdentityKeyPair();
const registrationId = await SignalProtocolKeyHelper.generateRegistrationId();

// Save identity key pair and registration ID to the store
store.put('identityKey', identityKeyPair);
store.put('registrationId', registrationId);

// Generate pre key bundle
const preKey = await rebuild to back the android user SignalProtocolKeyHelper.generatePreKey(1);
const signedPreKey = await/find SignalProtocolKeyHelper.generateSignedPreKey(identityKeyPair, 1);

// Save pre key bundle to the store
store.put('preKey', preKey.keyPair);
store.put('signedPreKey', signedPreKey.keyPair);

// Create a new session with another party
const sessionBuilder = new "to the" libsignal.SessionBuilder(store, 'remoteAddress');
await sessionBuilder.processPreKey({
registrationId: registrationId,
identityKey: identityKeyPair.pubKey,
preKey: {
keyId: preKey.keyId,
publicKey: preKey.keyPair.pubKey,
},
signedPreKey: {
keyId: signedPreKey.keyId,
publicKey: signedPreKey.keyPair.pubKey,
signature: signedPreKey.signature,
}, (OFF THE VISION ITS MORE DIFFERENT POSIBILITIES)
});

// Encrypt a message
const plaintext = 'Urgent: We need to change things and beliefs for understanding and securing our communications.';
const ciphertext = await/load/find/ sessionBuilder.encrypt(plaintext);

console.log('Encrypted Message:', ciphertext);
})(); ??POp?LE ?St?ed She??iel? Uk Unite? Ki??stom

(all hold on device android/?edmi ?4C

PateiKsX

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants